OIDC Integration

Use this skill to design or implement authentication flows that rely on an OpenID Connect provider.

Objective

Help the user integrate OIDC in a way that matches their architecture, avoids unsafe defaults, and produces code that fits the current stack instead of dumping generic samples.

Working Style

Start by identifying the actual integration shape before writing code.

Check these points first:

• Which side owns auth state: SPA only, backend session, or BFF.
• Which provider is involved: Keycloak, Auth0, IdentityServer, Authing, Azure AD, or another OIDC-compliant IdP.
• Whether there is one provider or multiple providers.
• Whether the client is public or confidential.
• Whether refresh tokens are required.