Recipes / Federation
Federation · 11 recipes
Federation
Templates for Okta, Entra ID, Google Workspace, SAML, and more.
- auth0-with-hub-upstream
auth0-with-hub-upstream
Add Thoryn Hub as a Custom OIDC connection in your existing Auth0 tenant
Customer keeps Auth0 as the user-facing IdP and adds Thoryn Hub as an upstream OIDC connection. The reverse of `auth0-as-source` — use it when migration is years away but EUDIW is needed today.
- auth0
- oidc
- idp
- hub-upstream
- okta-with-hub-upstream
okta-with-hub-upstream
Add Thoryn Hub as an OIDC IdP in your existing Okta tenant
Customer keeps Okta as the user-facing IdP and adds Thoryn Hub as an upstream OIDC identity provider — the EUDIW + verifiable-credential gateway behind the Okta login. The reverse of `okta`.
- okta
- oidc
- idp
- hub-upstream
- auth0-as-source
auth0-as-source
Auth0 as a Hub federation source — migration overlay
Federate Hub to an existing Auth0 tenant during a migration window. Customers stay logged in via Auth0; Hub takes over gradually.
- auth0
- oidc
- idp
- migration
- generic-oidc
generic-oidc
Generic OIDC IdP as a Hub federation member
Catch-all template for federating Hub to any OIDC-conformant IdP — public-cloud providers, regional IdPs, internal identity stacks.
- oidc
- idp
- generic
- generic-saml
generic-saml
Generic SAML 2.0 IdP as a Hub federation member
Federate Hub to any SAML 2.0 IdP — long-tail enterprise IdPs, custom corporate identity providers, ADFS, etc.
- saml
- idp
- generic
- google-workspace
google-workspace
Google Workspace as a Hub federation member
Federate Hub to a Google Workspace tenant. Common at small-mid SaaS customers.
- google-workspace
- oidc
- idp
- jumpcloud
jumpcloud
JumpCloud as a Hub federation member
Federate Hub to a JumpCloud directory. The simplest of the seven pre-built connectors — JumpCloud uses one global OAuth issuer, so only client-id and client-secret are needed.
- jumpcloud
- oidc
- idp
- keycloak
keycloak
Keycloak as a Hub federation member
Self-hosted shops federate their Keycloak realm into Hub via standard OIDC. Common at developer-heavy customers and EU public-sector orgs.
- keycloak
- oidc
- idp
- self-hosted
- linkedin
linkedin
LinkedIn as a Hub federation member
Add LinkedIn social sign-in via OIDC. Two LinkedIn quirks shape the setup — email is a separate scope, sub is opaque per app.
- oidc
- social
- idp
- entra-id
entra-id
Microsoft Entra ID (Azure AD) as a Hub federation member
Federate Hub to an Entra ID tenant. Most-common enterprise scenario in DACH and the UK.
- entra-id
- azure-ad
- oidc
- idp
- okta
okta
Okta as a Hub federation member (OIDC)
Federate Hub to an Okta tenant. Okta authenticates the user; Hub issues the OAuth2 / OIDC tokens to your relying parties.
- okta
- oidc
- idp