Submit a ticketCall us

Quickly Address Software Vulnerabilities
Patch Manager is an intuitive patch management software which extends the capabilities of WSUS and SCCM to not only patch Windows® servers and workstations, and Microsoft® applications, but also other 3rd-party applications which are commonly exploited by hackers. Learn More.

 

Home > Success Center > Web Help Desk (WHD) > Web Help Desk Administrator Guide > Set up the application > Configure your authentication settings

Configure your authentication settings

Created by Steve.Hawkins, last modified by Anthony.Rinaldi on Jul 18, 2016

Views: 62 Votes: 0 Revisions: 5

You can use the Authentication Settings to configure the authentication methods used to access Web Help Desk.

If you plan to install FIPS 140-2 compliant cryptography in your deployment, you can use the Password Security Migration Tool to encrypt all client and tech account passwords to FIPS 140-2 cryptography prior to activation. The migration tool invalidates all stored client and tech passwords that use a weaker cryptography standard. All clients and techs who did not log in to Web Help Desk before their planned migration date will not be able to log in, and must reset their passwords by clicking Forgot Password on the Log In page. Password recovery is available only if Web Help Desk authentication method and the Show Forgot Password Button checkbox are selected in the screen.

Configure your authentication method and settings

  1. In the toolbar, click Setup and select General > Authentication.
  2. Complete the fields and selections in the top portion of the screen as required, then click Save.

    Click the tooltips for more information.

The following table describes the authentication methods you can select in the screen.

Authentication method Description
Web Help Desk Authenticates the user with the user name and password. User names and passwords are pulled from the Web Help Desk database or imported from Active Directory or LDAP connections.
CAS 2.0
(Central Authentication Service)

Uses a single sign on (SSO) service URL to authenticate the user provided by Web Help Desk. The CAS server sends the user back to Web Help Desk and attaches a "ticket" to the Web Help Desk URL. Web Help Desk submits the ticket to the CAS validate URL to obtain the user name of the authenticated user.

See Deploy SSO with CAS 2.0 for information on how to set up CAS 2.0 on your Web Help Desk Tomcat server.

Servlet Authentication
(for Apache Tomcat installations)

Provides the authenticated user name to Web applications using the HttpServletRequest.getRemoteUser() method.

You can use Windows Authentication Framework Light Edition (WAFFLE) at your own risk for Web Help Desk servlet authentication. SolarWinds does not support this method of SSO.

For information about configuring WAFFLE, see Servlet Single Sign On Security Filter at the GitHub Website.

HTTP Header Uses Web servers (such as the Apache HTTP Server) to forward externally authenticated user information using HTTP headers.
HTTP Form Value Forwards the authenticated user name through an HTTP name/value pair instead of an HTTP header.

Encrypt passwords using the Password Security Migration Tool

If you install FIPS 140-2 cryptography in an existing deployment, you can use the Password Security Migration Tool to ensure that all client and tech account passwords are migrated to FIPS 140-2 cryptography.

Click the tooltips for more information.

 
Last modified
13:52, 18 Jul 2016

Tags

Classifications

Public