Choose Self-Hosted Identity and Secret Services
Evaluate an identity provider and secret manager independently, and prove workload access, administrative recovery, and restoration.
List who needs to sign in, who runs workloads, which applications consume identity assertions, and which applications need secrets. Separate an identity provider such as Keycloak from a secret service such as OpenBao. The former can issue identity assertions, manage sessions, and federate users. The latter governs read and rotation of sensitive values under its configured auth methods and policies. A shared host or sign-in flow does not justify giving users broad access to secrets. ## Key Points - [Keycloak administration](https://www.keycloak.org/docs/latest/server_admin/) - [Keycloak admin recovery](https://www.keycloak.org/server/bootstrap-admin-recovery) - [OpenBao integrated storage](https://openbao.org/docs/configuration/storage/raft/)
skilldb get auth-services-skills/self-hosted-identity-and-secretsFull skill: 31 linesChoose Self-Hosted Identity and Secret Services
Inventory two separate services
List who needs to sign in, who runs workloads, which applications consume identity assertions, and which applications need secrets. Separate an identity provider such as Keycloak from a secret service such as OpenBao. The former can issue identity assertions, manage sessions, and federate users. The latter governs read and rotation of sensitive values under its configured auth methods and policies. A shared host or sign-in flow does not justify giving users broad access to secrets.
Record organization boundaries, deployment ownership, trust roots, versions, and required dependencies. Decide whether the use case needs OIDC, SAML, workload identity, dynamic credentials, or a specific audit trail. Compare the documented edition and release for those requirements. Include ongoing operating costs for certificate rotation, patches, backups, and staff access. A self-hosted service needs explicit ownership even when software licensing is free.
Exercise identity and workload policy
Build a staging fixture with one application and one secret. Configure the identity provider with an approved test client and exact callback destinations. Confirm that a permitted fixture account reaches the app, and that a disabled or unauthorized test user cannot. Test the role claims the application actually consumes. Avoid copying claims or access tokens into diagnostic logs.
Give the fixture workload a distinct service identity. Grant access only to its specific secret path or operation and record expiry and rotation behavior. Verify one successful read using a synthetic value. Attempt the same lookup with a second fixture workload without the grant and confirm it receives no data. Check whether administrator privileges are held only by the existing designated accounts and what happens when a service identity is revoked.
Plan restoration before trusting the pair
Document an isolated restore drill for each service. Identify the required snapshot, keys or recovery material, certificates, external database, and version constraints. Record how an operator recovers administrative access without introducing a permanent shared credential. Test from a clean instance or isolated staging copy using dummy values and preserve evidence without the secret material.
Report the exact capabilities tested, deployment dependencies, backup age, restoration outcome, and who owns each incident class. Keep production access behind its existing approval boundary. A successful login establishes authentication for the tested client. Successful access denial and recovery drills establish additional operational properties independently.
References
Install this skill directly: skilldb add auth-services-skills
Related Skills
Stytch
Build with Stytch for passwordless and modern authentication. Use this skill when the project needs to integrate Stytch for magic links, OTPs, OAuth, passkeys, biometrics, session management, or B2B organization auth. Covers the Stytch Node SDK, passwordless flows, session management, and B2B multi-tenancy.
Supabase Auth
Integrate Supabase Auth for user authentication and authorization in web applications. Use this skill when you need a full-featured, secure, and easy-to-use authentication solution with OAuth, email/password, magic links, and robust session management, tightly integrated with a PostgreSQL database and other Supabase services.
Workos
Build with WorkOS for enterprise SSO and authentication. Use this skill when the project needs to integrate WorkOS for SAML/OIDC single sign-on, directory sync (SCIM), admin portal, AuthKit, or enterprise-ready identity features. Covers WorkOS AuthKit, SSO, directory sync, admin portal, and user management.
Auth0
Build with Auth0 for enterprise authentication and identity. Use this skill when the project needs to integrate Auth0 for SSO, OAuth, SAML, MFA, passwordless login, machine-to-machine auth, role-based access control, or enterprise identity federation. Covers the Auth0 Next.js SDK, React SDK, Management API, Actions, and RBAC.
Clerk
Build with Clerk for authentication and user management. Use this skill when the project needs to integrate Clerk for sign-up, sign-in, OAuth, MFA, session management, organization multi-tenancy, webhooks, or pre-built UI components. Covers the Clerk React SDK, Next.js middleware, server-side auth, webhooks, organizations, and custom flows.
Cognito
Build with Amazon Cognito for authentication and user management. Use this skill when the project needs User Pools for sign-up/sign-in, Identity Pools for AWS resource access, OAuth/OIDC federation, hosted UI or custom auth flows, token handling, or API Gateway integration. Covers the AWS Amplify Auth library, direct Cognito SDK usage, and securing backend APIs with Cognito tokens.