Identity connections in FoxIDs
FoxIDs connects an upstream identity source to a downstream application through two independently configured sides. An authentication method signs in a user locally or trusts an external identity provider. An application registration represents the application or API that trusts FoxIDs.
This separation lets an IAM administrator change the upstream identity provider without redesigning the application integration. FoxIDs can also translate claims and bridge identity protocols when the two sides use different standards.
Authentication method
Authentication methods define how users authenticate. They include the built-in login experience, OpenID Connect, SAML 2.0, WS-Federation, Directory Connector-backed passwords and links to other FoxIDs environments.
Start with Authentication methods to choose an upstream identity source and understand session behaviour.
Application registration
Application registrations define the client, application or API receiving tokens or SAML responses from FoxIDs. Supported downstream protocols include OpenID Connect, OAuth 2.0, SAML 2.0 and WS-Federation.
Start with Applications to choose a registration type and then open the protocol-specific configuration guide.
JWT and SAML
FoxIDs normalizes claims internally as JWT claims. See JWT and SAML for how SAML 2.0 claims are converted between authentication methods and application registrations.