Submit a ticketCall us

AnnouncementsChange Is Inevitable

Get valuable help when it comes to tracking and monitoring changes. SolarWinds® Server Configuration Monitor (SCM) is designed to help you: detect, track, and receive alerts when changes occur, correlate system performance against configuration changes, compare server and application configuration against custom baselines, and verify application and system changes.

Learn more.

Home > Success Center > Web Help Desk (WHD) > WHD - Knowledgebase Articles > Unable to Use Single Sign On in Web Help Desk

Unable to Use Single Sign On in Web Help Desk

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 2,348 Votes: 0 Revisions: 10

Issue:

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

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

Last modified

Tags

Classifications

Public