Configuring Single Sign-on (SSO) using SAML 2.0 for ADFS

Single Sign-On (SSO) is an authentication method that allows users to sign in with a single ID and Password. ManageEngine PAM360 offers support for SSO using SAML 2.0, which facilitates integration with Federated Identity Management Solutions for Single Sign-on (SSO). PAM360 acts as the Service Provider (SP) and it integrates with Identity Providers (IdP) using SAML 2.0. The integration basically involves supplying details about SP to IdP and vice-versa. Once you integrate PAM360 with an IdP, the users have to just login to IdP and then, they can automatically login to PAM360 from the respective identity provider's GUI without having to provide credentials again.

Note: PAM360 allows users to configure SAML SSO for Secondary server as a service provider, which allows users to log in to PAM360 using the Secondary server when Primary is down.

Configuring SSO using SAML is a two step process involving the following topics:

  1. Steps to Configure ADFS 10.0
  2. Steps to Configure PAM360 to Enable SSO Services

1. Steps to Configure ADFS 10.0

Active Directory Federation Services (ADFS) created by Microsoft runs on Windows and supports SAML integration to provide SSO services to systems and applications throughout the organization. A similar configuration can be achieved in PAM360 as well. For this, you need to first integrate ADFS with PAM360 followed by enabling SSO services.

Steps in Detail:

  1. Log in to PAM360 and navigate to Admin >> SAML Single Sign On. In the SAML SSO configuration page, download the service provider metadata.xml file available under step 1.
  2. Navigate to Start >> All Programs >> Administrative Tools, and open ADFS 10.0 Management.
  3. The first step is to add Trust Relationships in ADFS 10.0 to add PAM360 details. Under Trust Relationships, right-click on Relying Party Trusts and select Add Relying Party Trust from the drop down menu. A Add Relying Party Trust Wizard appears on the screen.

    1. Click Start and click Select Data Source from left pane.
    2. Choose the second option, Import data about the relying party from a file.
    3. Click Browse to import the metadata.xml file downloaded earlier from PAM360, and click Next.

    4. Set a Display name for the relying party, i.e. PAM360 and click Next.

    5. Choose Access Control Policy: Select Permit everyone and click Next.

    6. Skip the Ready to Add Trust step by clicking Next and then click Close.
  4. PAM360 will now be displayed in the Relying Party Trusts list. Right-click on the same and select Properties from the drop down menu as shown below.

  5. In the dialog box that opens, switch to the Advanced tab and select SHA 1 as the secure hash algorithm. Apply changes and click Ok.

  6. Right-click on PAM360 again and now select Edit Claim Insurance Policy.
  7. In the dialog box that opens,
    1. Click Add Rule under Issuance Transform Rules.
    2. Select Transform an Incoming Claim as the Claim rule template and click Next.
    3. Under Configure Claim Rule,
      1. Enter NameID as the Claim rule name.
      2. Select Windows account name as the Incoming claim type.
      3. Select Name ID as the Outgoing claim type.
      4. Select Transient Identifier for Outgoing name ID format.
    4. Click Finish.
  8. Click Apply to save changes and close the Edit Claim Rules window by clicking Ok.

Now, you have successfully configured ADFS in PAM360. Proceed to step 2 below to know how to enable SSO services in PAM360.

    Note: If you have already imported users to PAM360 from AD, then their login names will be stored in the format, DOMAIN\Loginname. By default, setting Windows account name as the incoming claim type will match this format. However, if you have created PAM360 local accounts for your AD users by importing them via a CSV file, you need to instead select a different claim type that matches the login name format stored in PAM360.

2. Steps to Configure PAM360 to Enable SSO Services

  1. Open PAM360 and navigate to Admin >> Authentication >> SAML Single Sign-On.
  2. Under Step 2 in the page, choose the first option Upload IdP metadata file to browse and open ADFS's Federation.xml file.
  3. Notes:

    1. The XML file can be downloaded from ADFS 10.0 console. In the console's left navigation pane, click on Endpoints and scroll down to the Metadata list. Now, locate the URL Path provided for the Federation Metadata type in this list and open the URL in a new browser tab to download the metadata XML file.
    2. For SAML SSO authentication, the Assertion Consumer URL is the hostname of the server, by default. To update the Assertion URL, follow the below steps:
      1. Go to Admin >> Settings >> Mail Server Settings.
      2. Under Access URL, update the required URL and click Save. Now, the Assertion Consumer URL under Service Provider Details will be updated.
  4. The uploaded XML file will also populate the certificate details required for Step 3. In case the details aren't auto-filled in upon providing the metadata file, try configuring the Identity Provider details manually in Step 2 and 3. Then, click Save.
  5. To configure SAML Single Logout, navigate to <PAM360_Installation_Directory\PAM360\conf\system_properties.conf> and append the following system property under the existing properties.
    • saml.logout.redirect.slo=true


    1. SAML Single Logout is applicable from PAM360 build 5304 and above only.
    2. If you have already configured SAML for PAM360, re-upload the metadata.xml file to configure Single Logout.
  6. ADFS SSO service is now successfully configured for PAM360. Click on Enable SAML SSO to activate the service.
  7. Log out and log back in to PAM360 to test the configuration.