Submit a ticketCall us

WebinarUpcoming Webinar: Should I Move My Database to the Cloud?

So you’ve been running an on-premises SQL Server® for a while now. Maybe you’ve moved it from bare metal to a VM, and have seen some positive benefits. But, do you want to see more? If you said “YES!”, then this session is for you, as James Serra will review the many benefits that can be gained by moving your on-prem SQL Server to an Azure® VM (IaaS). He’ll also talk about the many hybrid approaches, so you can gradually move to the cloud. If you are interested in cost savings, additional features, ease of use, quick scaling, improved reliability, and ending the days of upgrading hardware, this is the session for you.

Register now.

Home > Success Center > Web Help Desk (WHD) > WHD - Knowledgebase Articles > Configure Single Sign On for Web Help Desk using Active Directory Federation Services

Configure Single Sign On for Web Help Desk using Active Directory Federation Services

Table of contents

Updated: November 1, 2017



This article describes how to configure single sign on for WHD using Active Directory Federation Services (AD FS). 

Web Help Desk supports SAML 2.0, which allows single sign-on (SSO) authentication. SSO in Web Help Desk uses Active Directory Federation Services (AD FS) to authenticate a user over multiple Web applications over the life of a single online session. When you configure SSO in Web Help Desk using AD FS, you can enable users who log in to the Microsoft Exchange server to be automatically logged in to Web Help Desk as well.

AD FS 1.0, which is the default on Windows Server 2008 R2, does not support SAML 2.0. If you are using Windows Server 2008 R2, you must upgrade to AD FS 2.0.


  • WHD and later
  • SAML 2.0


  1. Enable automatic Active Directory (AD) logon through Windows by adding the AD FS logon URL to the Local Intranet sites within Internet options. This can also be done through a group policy for the whole organization.
    See About URL Security Zones (© 2017 Microsoft, available at, obtained on February 17, 2017).
  2. Set up your SAML server with an identity repository (such as AD FS or LDAP) in the remote login URL for your SAML server.
  3. Enable SSL in your WHD installation using a trusted certificate (like GoDaddy™ or VeriSign®) or create your own certificate.
    For additional information, see Manage keys and certificates.


For additional information, see the following articles:


Last modified