winuxguy

Ahhhmmm... pack some sandwiches and go...

this might already be possible with REST API since Jira supports REST API too. haven't tested but it's a huge possibility.

Have you guys tried to connect to your LDAP with port 636 on the Serv-U LDAP config? I mean, if your LDAP requires SSL on port 636 and an application connects to that port with SSL then it should not allow the connection but the current version of Serv-U can connect to LDAP/AD if you put port 636, that may mean that Serv-U…

Darn... Got to have this! LOL!!!

bummer... looks like my LDAP server might not have the strict configuration to only use LDAPS for port 636...

Java 6 and below due to support of SSLv3 and no complete support for TLS 1.1 and TLS 1.2

that's fine mate. Have you followed conners‌ advise? Did that work for you?

This is a great and working solution for WHD 11.2.1 indeed! Here, you hit 2 good upgrades, the Java 7 with full TLS support and Tomcat 7.0.63.

You may certainly do these (service webhelpdesk stop): 1. Stop WHD after install 2. Edit the file /usr/local/webhelpdesk/conf/whd.conf and look for the line below: PRIVILEGED_NETWORKS= and set it to: PRIVILEGED_NETWORKS=* 3. Save the file and start WHD (service webhelpdesk start) If you are done with the initialization,…

Unfortunately, I don't think there is a way to fix it in WHD 11.0.4. You may at least upgrade to 12.1. Although I have not tried running WHD 11.0.4 in JRE7 but I am a bit sure that it will not run due to the Tomcat version included.

There was a KB already written for disabling SSLv3 and enabling TLS on the link below: http://knowledgebase.solarwinds.com/kb/questions/5998/Protecting+Against+%22POODLE%22+security+vulnerability+(CVE-2014-3566)‌ From that KB, you only need to do the following: * Download and install Java 7, as described in:*…

Thanks for that update clearcircuit‌. This should greatly help everyone.

What if the issue only happens to a handful of users and creating a new account in DRS Centralized Server is still resulting to the same error?

I think this "hack" is only working with WHD version 12.2 and up. I did some testing of MacOS X upgrade to 10.10 with WHD version 12.1 and version 12.2. The WHD version 12.1 requires the Java 6 update for MacOS X 10.10

This is great info. Thanks Jeff!

I hope you can get a screenshot for this too. Thanks

Tried the same on a newly installed 12.2 that is enabling Replace Default CSS option, it did not cause an issue to me. Just downloaded the template recently. Not sure if there are any changes. I don't even have a hotfix installed (if that makes any difference).

Would be great if the pictures are available.

Hi, Try the following: 1. Do not set anything in the Signature nor Encryption tabs of the RP settings 2. In your ADFS server, export the "Token-signing" certificate and use that for the Verification certificate in "Setup > General > Authentication" Then for the logout if you'd like to use that too: 0. open ADFS Managment…

It's probably taking it from the very last connection that WHD is able to trace from and may not necessarily be the local machine's IP address. That's the only thing I can think off. The logic from behind on how it does things, that will have to be checked from the codes.

UPDATE! remove the following: - "TLS_ECDHE_RSA_WITH_RC4_128_SHA" - "TLS_RSA_WITH_RC4_128_MD5" - "TLS_RSA_WITH_RC4_128_SHA" from the list of ciphers if you get the following rate from SSLLabs scan result: This server uses RC4 with modern browsers. Grade capped to C.

WebHelpDesk version 12.3 has a hotfix 1 and it includes instructions for changing the ciphers.

Once you have already "un-deleted" that ticket, you can prevent WHD from deleting merge tickets by doing the following: - go to Setup > Ticket > Status Types - create a new status say "Merged" - on the same page, click "Options" tab - set "When Tickets Are Merged" to "Set Status of Child Tickets to" then select "Merged"…

Unfortunately, there isn't a way within WHD for a client assigned to an asset to confirm it. That process will not be automated in WHD but that is indeed a good Feature to Request for

Removing records directly from the database requires expertise on DB Administration since there will be a lot of constraints that you have to mind. I would suggest to go for deleting those clients from the web UI...

Hmm... that is a bit odd. The request Type field is by default a required field and the ticket will not be saved if the client will not select all throughout the sub-request types. Maybe a few more info would help like which version are you running, was it just the clients or also techs are doing this or maybe you could be…

This is not doable in WHD unless the you are willing to get a Tech License for a client to be able to login and search all tickets assigned to you then that would be the best case. Have you also checked if the Client Admin setup would work for you?

You may also use Action Rules to Modify the ticket to changing the Status type to Resolved at least if the request type is of specific ones. You can then specify that Action Rule to run on Tech Update only. Hope that helps.

I am afraid that cannot possibly be changed. You may have to just send a request for that feature for now.

CAS will need to be configured to allow authentication to your AD/LDAP and it will still ask for a login but will SSO you to WHD once you have successfully logged in. The way CAS works is that you can use it for a single sign-on for various applications wherein you will have a single/common login screen for all of them and…