FoxIDs is configured with up-parties and down-parties. Up-parties authenticate the internal users or optionally by trust to an external Identity Provider (IdP). Applications and APIs are connected to FoxIDs as down-parties.
There are four different party types:
FoxIDs support tree different up-party types:
Each up-party creates a session when a user is authenticated. All sessions are separately connected to an up-party. There are two different kinds of sessions. A login up-party create a user session. An OpenID Connect up-party and SAML 2.0 up-party create an up-party session which only holds information to enable logout.
Both session types lifetime, absolute lifetime and persistence (if the session should be saved when the browser is closed) can be configured.
FoxIDs support tree different down-party types:
JWT and SAML
OpenID Connect, OAuth 2.0, JWT and JWT claims are first class citizens in FoxIDs. Internally claims are always represented as JWT claims and request / response properties are described with OAuth 2.0 and OpenID Connect attributes.
FoxIDs converts between standards where attributes are converted to the same internal representation using JWT claims and OAuth 2.0 / OpenID Connect attributes.
Therefor, SAML 2.0 claims is internally converted to JWT claims between up-party and down-party.