How to connect
An IdP is connected with a up-party and an application or API is connected with a down-party.
It is possible to interconnect FoxIDs tracks either with a track link or OpenID Connect:
- Connect two FoxIDs tracks in a tenant with a track link
- Connect two FoxIDs tracks in the same or different tenants with OpenID connect
Up-party - How to connect Identity Provider (IdP)
An Identity Provider (IdP) can be connected with an OpenID Connect up-party or an SAML 2.0 up-party. An Identity Provider (IdP) is more precisely called an OpenID Provider (OP) if configured with OpenID Connect.
All IdPs supporting either OpenID Connect or SAML 2.0 can be connected to FoxIDs. The following is how to guides for some IdPs, more guides will be added over time.
OpenID Connect up-party
Configure OpenID Connect up-party which trust an external OpenID Provider (OP) - an Identity Provider (IdP) is called an OpenID Provider (OP) if configured with OpenID Connect.
How to guides:
- Connect Azure AD
- Connect Azure AD B2C
- Connect IdentityServer
- Connect Signicat
- Connect Nets eID Broker
SAML 2.0 up-party
Configure SAML 2.0 up-party which trust an external SAML 2.0 Identity Provider (IdP).
How to guides:
- Connect AD FS
- Connect PingIdentity / PingOne
- Connect NemLog-in (Danish IdP)
- Connect Context Handler (Danish IdP)
Up-party - How to connect relying party (RP)
// TODO