Like what you see? Have a play with our trial version.

This section is related to the active directory federation services (AD FS) configurations required for your Yellowfin SAML bridge.


AD FS Public Key

You will need to obtain a valid public key from AD FS (.cer file) to sign SAML requests coming from Yellowfin. This key is then set in the, in the form of a text. For example: 

onelogin.saml2.idp.x509cert =MIIC2DCCAcCgAwIBAgIQfdRAAWmWko1IsimA004o3TANBgkqhki…


Download signing certificate from AD FS:

  1. Find the certificate in the AD FS

  2. Select ‘View Certificate’.
  3. Go to ‘Details’.
  4. Click ‘Copy to file’. 
  5. Then open the file in a text editor and copy the string to onelogin.saml2.idp.x509cert.




Registering Yellowfin SAML Bridge Identity Provider in AD FS

To register Yellowfin SAML bridge service provider, use samlbridge/metadata.jsp. You need to provide it in the form of a URL, for instance: http://yellowfin:8080/samlebridge/metadata.jsp. Ensure that you can access the URL from AD FS server. It pulls the details coming from samlbridge/WEB-INF/classes/

Note. Each time when you modify, you need to update the Yellowfin Relying Party Trust metadata in AD FS.

More details about registering service provider in AD FS can be found via


Add Relying Party Trust

  1. Go to ‘Trust Relationship’ in AD FS manager, click on ‘Relying Party Trust’ and choose ‘Add Relying Party Trust Wizard’.
  2. Select the ‘Import data about the relying party published online or on a local network’ radio button. Type into ‘Federation metadata address (host name or URL) the URL to Yellowfin SAML Bridge metadata.jsp file. For instance, http://yellowfin:8080/samldridge/metadata.jsp. This will become your service provider entity id (onelogin.saml2.sp.entityid) to fill in file.

  3. On the ‘Select Data Source’ page, provide a displayed name for the service provide:

  4. This is going to be an application name visible for a user as well as part of the SSO URL in the file:

    onelogin.saml2.idp.single_sign_on_service.url = https://adfs.local/adfs/ls/IdpInitiatedSignon.aspx?loginToRp=Yellowfin

  5. On the next page, select ‘I do not want to configure multi-factor authentication settings for this relying party trust at this time’. Configuring multi-factor authentication is beyond this scope. Click ‘Next’.

  6. Select the ‘Permit all users to access this relying party’ radio button. Click ‘Next’ to the end.

  7. Once you have registered the Yellowfin SAML Bridge in AD FS, you’ll be offered to set claim rules. See below for more information on those.


Claim Rules

Note: SAML requires Name ID as part of the AD FS response, ensure that you pass it correctly in a proper format.

For instance, you define name id in like below:

onelogin.saml2.sp.nameidformat = urn:oasis:names:tc:SAML:1.1:nameid-format:emailAddress

That means you need to pass an email address as a name ID from the AD FS. Your claim rules should look like below.


Request AD attributes

  1. Click ‘Add Rule’ and choose ‘Sent LDAP Attributes as Claims’.
  2. Provide it with the name and add all the attributes you want to pass to the SAML Bridge.
  3. To do automatic user provision via SAML Bridge, you need to pass at least email address, user name, user surname.
  4. You need to pass a proper user ID corresponding to the Yellowfin authentication method (either name ID or email addresses).
  5. Make sure that whatever you pass as email addresses attribute indeed keeps email addresses. It can be User-Principal-Name or E-Mail-Addresses.

  6. Note: You may want to add more AD attributes to be able to do user provision via SAML Bridge like default user role, group memberships etc. Additional modification to SAML Bridge web.xml and acs.jsp files will be required.


Transform email address into name ID

  1. Click ‘Add Rule’. This time, select ‘Transform an Income Claim’ this time. 
  2. Select ‘E-Mail Address’ as the ‘Incoming claim type’. 
  3. Then select ‘Name ID’ as the ‘Outgoing claim type’ and ‘Email’ as ‘Outgoing name ID format’ (this should correspond to onelogin.saml2.sp.nameidformat of file).




SSO service (IdpInitiatedSignOnPage)

AD FS 2.0 provides the IdpInitiatedSignOn.aspx page to handle SAML-based IDP-initiated single sign-on (SSO). This functionality enables a user to sign on locally to the AD FS 2.0 server using the SAML protocol or to sign on to Web SSO-compatible relying party (RP) applications like Yellowfin.

This is set in the, in the form of a URL, as shown below:

onelogin.saml2.idp.entityid = https://<ADFS domain name>/adfs/ls/IdpInitiatedSignon.aspx?loginToRp=<RP>

onelogin.saml2.idp.single_sign_on_service.url = https://<ADFS domain name>/adfs/ls/IdpInitiatedSignon.aspx?loginToRp=<RP>


Where, <RP> is the displayed name which you defined during registering Yellowfin SAML Bridge service provider in AD FS.

More information about IdpInitiatedSignOn.aspx can be found here:








  • No labels