FoxIDs

SAML 2.0

FoxIDs can both act as a SAML 2.0 IdP and RP.

The FoxIDs SAML 2.0 metadata only include logout and single logout information if logout is configured in the SAML 2.0 up og down party.

How to:

IdP

(identity provider) //TODO

RP

(relying party also called SP, service provider) //TODO

Connect AD FS as RP

AD FS can be connected to FoxIDs with SAML 2.0 acting as an RP where and FoxIDs is acting as an IdP.

Configuring AD FS as RP in the following steps.

1) AD FS as a SAML 2.0 RP on FoxIDs

First the AD FS SAML 2.0 RP is configured in a FoxIDs track as an SAML 2.0 down party through FoxIDs Control. The RP down party can either be configured by adding the SAML 2.0 details or using the AD FS metadata https://...adfs-domain.../federationmetadata/2007-06/federationmetadata.xml (future support).

2) FoxIDs as a SAML 2.0 IdP on AD FS

After configuring the AD FS SAML 2.0 down party in a FoxIDs track an SAML 2.0 IdP metadata is exposed, which can be used to configure FoxIDs as a IdP on AD FS.

FoxIDs SAML 2.0 IdP metadata https://foxids.com/tenant-x/track-y/adfs-rp-party/saml/idpmetadata
for 'tenant-x' and 'track-y' with the down party name 'adfs-rp-party'

Alternatively, FoxIDs can be configured manually as an IdP on the AD FS with the following information's:

  • The public FoxIDs track ('tenant-x' and 'track-y') certificate
  • Hash algorithm, default SHA-256
  • The FoxIDs track identifier https://foxids.com/tenant-x/track-y or another configured identifier
  • Single sign-on service endpoint https://foxids.com/tenant-x/track-y/(adfs-idp-party)/saml/authn
  • Single logout service endpoint https://foxids.com/tenant-x/track-y/(adfs-idp-party)/saml/logout

3) FoxIDs issuances claims

FoxIDs default issue the user's identity in the NameID claim with format persistent.

Connect AD FS as IdP

AD FS can be connected to FoxIDs with SAML 2.0 acting as an IdP where and FoxIDs is acting as an RP.

Configuring AD FS as IdP in the following steps.

1) AD FS as a SAML 2.0 IdP on FoxIDs

First the AD FS SAML 2.0 IdP is configured in a FoxIDs track as an SAML 2.0 up party through FoxIDs Control. The IdP up party can either be configured by adding the SAML 2.0 details or using the AD FS metadata https://...adfs-domain.../federationmetadata/2007-06/federationmetadata.xml (future support).

Recommended SAML 2.0 bindings

  • Authn request and response binding: Post
  • Logout request and response binding: Post

It is also sometimes recemented to use an authn request redirect binding, but the long query string can give problems I some devices.

2) FoxIDs as a SAML 2.0 RP on AD FS

After configuring the AD FS SAML 2.0 up party in a FoxIDs track an SAML 2.0 RP metadata is exposed, which can be used to configure FoxIDs as a RP on AD FS.

FoxIDs SAML 2.0 RP metadata https://foxids.com/tenant-x/track-y/(adfs-idp-party)/saml/spmetadata
for 'tenant-x' and 'track-y' with the up party name 'adfs-idp-party'

Alternatively, FoxIDs can be configured manually as an RP on the AD FS with the following information's:

  • The public FoxIDs track ('tenant-x' and 'track-y') certificate
  • Hash algorithm, default SHA-256
  • The FoxIDs track identifier https://foxids.com/tenant-x/track-y or another configured identifier
  • Assertion consumer service endpoint https://foxids.com/tenant-x/track-y/(adfs-idp-party)/saml/acs
  • Single logout service endpoint https://foxids.com/tenant-x/track-y/(adfs-idp-party)/saml/singlelogout

3) AD FS issuances claims

It is recommended to add the NameID (in AD FS called the NameIdentifier http://schemas.xmlsoap.org/ws/2005/05/identity/claims/nameidentifier claim) to enable the SessionIndex. Without the NamID AD FS do not add the SessionIndex to the SAML token and it will not be possible to do single logout.

FoxIDs require AD FS to issue the users identity in either the NameID or at least one of the following claims:

  • UPN http://schemas.xmlsoap.org/ws/2005/05/identity/claims/upn
  • Email http://schemas.xmlsoap.org/ws/2005/05/identity/claims/emailaddress
  • Name http://schemas.xmlsoap.org/ws/2005/05/identity/claims/name

Content