Tools

Unable to Use Single Sign On in Web Help Desk

Single Sign On (SSO) sources do not work in Web Help Desk (WHD) when using Apache. Instead use Apache on port 80 to get the REMOTE_USER header to determine a logged-in client, which authenticates the client without requiring a password.

First published date

10/25/2018 2:36 PM

Last published date

3/18/2020 7:29 AM

Overview

Single Sign On (SSO) sources does not work in Web Help Desk (WHD) when using Apache. Reconfiguring WHD to use IIS is also unsuccessful.

Product section

Web Help Desk

Cause

Web Help Desk (WHD) tries to authenticate users on the same port (8081) it uses for network communication.

Resolution

Use Apache on port 80 to get the REMOTE_USER header to determine a logged-in client. This method authenticates the client without requiring a password. The header passes to Tomcat and WHD, running on port 8081.

To enable this type of SSO authentication, switch WHD's authentication method in its settings to authenticate users and create an LDAP connection to access a client list. Based on their user names matching the REMOTE_USER header, users in the Active Directory (AD) user list are automatically logged in from the WHD URL.

For configuration and other details, please refer to Web Help Desk Forums’ Troubleshooting & Configuration: Single Sign On Setup

Disclaimer: Please note, any content posted herein is provided as a suggestion or recommendation to you for your internal use. This is not part of the SolarWinds software or documentation that you purchased from SolarWinds, and the information set forth herein may come from third parties. Your organization should internally review and assess to what extent, if any, such custom scripts or recommendations will be incorporated into your environment. You elect to use third-party content at your own risk, and you will be solely responsible for the incorporation of the same if any.