Submit a ticketCall us

WebinarWebinar: A checklist for planning your Network Performance Monitor (NPM) upgrade

Are you ready for your next upgrade? To help you plan smoothly, join this webcast to learn more about, SolarWinds® Orion® Installer, SolarWinds Upgrade Advisor, Upgrades Guides, Training Videos, and other resources available. We’ll share key upgrade planning considerations, lessons learned from customers with practical advice from SolarWinds Product Experts. We’ll also give practical tips to identify the estimated time needed and resources, how to prepare the business and IT staff for changes, ways to plan for required system changes, and more.

Register now.

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,411 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