Page History
Anchor | ||||
---|---|---|---|---|
|
This section covers the active directory federation services in detail.
AD FS Public Key
You will need to obtain a valid public keyfrom AD FS (.cer file) to sign SAML requests coming from Yellowfin. This key is then set in the onelogin.saml.properties, in the form of a text. For example:
...
SSO service (IdpInitiatedSignOnPage)
AD FS 2.0 provides the IdpInitiatedSignOn.aspx page to handle SAML-based IdPIDP-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 URL form and goes to onelogin.saml.properties, in the form of a URL, as shown below:
Code Block | ||
---|---|---|
| ||
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.
...