The latest version of Prism Central (v5.8) brought a bunch of new features. One of these features is the support for using an external Identity Provider (IDP) instead of or along side LDAP (Active Directory or OpenLDAP).

For this post I’ll be configuring ADFS for SSO to Prism Central.

Preliminary work

To make this whole process easier, grab the Federation XML from your ADFS site.
Head on over to https://federationURLHere/federationmetadata/2007-06/federationmetadata.xml and download the XML. You will need to substitute in your Federation URL (eg. This will download an XML document which contains the settings Prism Central needs to setup the connection.

Crete an A record for your Prism Central VM (eg. prism.domain.local).

Prism Central Configuration

Before you go any further, click on the link at the bottom of the Authentication window that says “Download Metadata”. This will download another XML for use later when we need to configure ADFS so keep this safe for the time being.

Once you have the XML, in Prism Central, head to the gear icon and select Authentication.

Now go ahead and click the New IDP button so we can configure the Prism Central side of things.

Now we can give our configuration a name (this name will be shown on the Prism Central login page) – I went with something super original, ADFS, and then click on the radio button for “Upload Metadata”. Once you click the radio button you’ll see an Import Metadata button. You do have the option to configure this manually if you can’t get the metadata for whatever reason.

Click the Import Metadata button and select the FederationMatadata.xml you downloaded earlier from your federation URL.

Once the XML has been uploaded, click Save.
you’ll be taken back to the Authentication Configuration page where you can see your configured IDP Authentication, in this case ADFS.

you can now go ahead and setup your Role Mappings for this new Authentication type. Note: When using IDP as opposed to LDAP, you cannot map roles to groups. Role mapping is done to an individual user not a group. For ADFS, this needs to be the users UPN. This is also case sensitive. So if your UPN has capitol letters, it must be exactly the same here.

Now that the Prism Central config is done, we can switch over to our ADFS server and configure the connector to Prism Central.

ADFS Configuration

Adding a Relaying Party Trust

The connection between ADFS and Prism Central is defined using a Relying Party Trust (RPT).

Select the Relying Party Trusts folder from AD FS Management, and add a new Standard Relying Party Trust from the Actions sidebar. This starts the configuration wizard for a new trust.

In the Select Data Source screen, select Import data from the relaying party from a file.

Choose the metadata file that was downloaded from Prism Central.

On the next screen, specify a display name.

You may configure multi-factor authentication on this next screen, but this is beyond the scope of this guide.

On the next screen, select the Permit all users to access this relying party radio button.

On the next two screens, the wizard will display an overview of your settings. On the final screen use the Close button to exit and open the Claim Rules editor.

Creating Claim Rules

Once the relying party trust has been created, you can create the claim rules and update the RPT with minor changes that aren’t set by the wizard. By default the claim rule editor opens once you created the trust.

To create a new rule, click on Add Rule. Create a Send LDAP Attributes as Claims rule.

On the next screen, using Active Directory as your attribute store, do the following:

  1. From the LDAP Attribute column, select User-Principal-Name.
  2. From the Outgoing Claim Type, select Name ID.

Click on OK to save the new rule.

Fort the most part, the ADFS config is now complete and should work when you go to Prism Central and select Login with ADFS. However I did notice that when logging in, it was sending the IP address of Prism Central to login to (which is fine on the same network). However, I wanted to adjust the trust so that the correct URL was sent and so I wouldn’t get SSL cert errors.

Adjusting the Trust Settings

With the ADFS Management screen still open, highlight your Prism Central trust and click properties in the action pane.

Switch to the Identifiers tab and add a new relying party identifier (this will be your DNS record for Prism Central).

Now switch to the Endpoints tab. You’ll notice that the SAML Assertion Consumer Endpoint is set to the IP address of the Prism Central VM. Highlight the SAML Assertion Consumer Endpoint and click edit.

Now, under the Trusted URL, enter your Prism Central DNS address instead of the IP address.

Click Ok to close the trust editor and give it a few minutes for Federation Sync to occur.

Head on over to Prism Central in your web browser and you should now see a Login with ADFS (or whatever you called it in Prism Central) button above the username/password fields.

And there you have it. You can now login to Prism Central with ADFS.


  1. ANTHONY MURFET June 27, 2019 at 12:49 am

    Good and useful article. Is it possible to use Azure AD Connect instead of ADFS for authentication? I can’t find that alternative mentioned anywhere. Thank you for you attention. Cheers, Anthony.

    1. William Beckett August 21, 2019 at 9:41 am

      Hi Anthony,
      If you have Azure AD Domain Services enabled on your Azure account you should be able to configure Secure LDAP access. Which means you should be able to use Azure AD as the IDP for Prism Central rather than an on-premises Active Directory.
      If I can get it working, I’ll create a new post detailing how to do it.


  2. Mark Adams October 15, 2019 at 1:22 am

    Thank you for this Will. Great instructions and it is working for us.

    I got caught out when adding this in our environment though. After adding this I was failing it log in.
    When you are adding the user into the “Role Mapping”, it is case sensitive. I added my own UPN into the value as lowercase, but my UPN in AD is a mixture of upper and lower case.

    Once I updated the value in “Roles Mapping” to completely match the case, it has worked perfectly.

    1. William Beckett October 22, 2019 at 10:01 am

      Hey Mark,
      No problem at all. I’m glad you got this working!
      Ah – Yes I did come across that as well. I’ll update the article now.


Leave A Comment

Your email address will not be published. Required fields are marked *