TokenIDP Documentation
TokenIDP is an OAuth 2.0 and OpenID Connect identity provider for multi-tenant applications, admin-managed client registrations, and standards-aligned token issuance.
Audience: Developers, CTOs, Marketing
Read this page if you need the top-level map of the TokenIDP documentation set.
Documentation Map
- Tutorials: step-by-step onboarding and first integration
- How-to Guides: task-focused guides for OAuth flows, SDKs, and deployment work
- Reference: supported specifications, endpoints, scopes, resources, and request details
- Explanation: security model, key management, and operational concepts
- Admin Portal: portal workflows for operators and tenant administrators
What TokenIDP Does
TokenIDP issues Access Tokens, Refresh Tokens, and ID Tokens for registered Applications in a Tenant. It exposes discovery metadata, JWKS publishing, /authorize, /token, /userinfo, /revoke, /introspect, /device_authorization, and /logout endpoints.
Recommended Reading Order
- Start with Getting Started.
- Configure your browser and API origins with Configure CORS.
- Choose the OAuth flow that matches your client type.
- Use the Reference section when you need exact endpoint behavior.
- Review Security Model before production go-live.
Working Example
curl https://id.example.com/.well-known/openid-configuration
Expected result: a JSON metadata document listing the Issuer, authorization endpoint, token endpoint, JWKS URI, supported grant types, and supported scopes.
Common Pitfalls
- Treating all client types the same. Public clients need PKCE and tighter redirect URI controls.
- Reusing development signing keys in production.
- Exposing overly broad scopes such as
api.full_accessto every Application.
Troubleshooting Tips
- If an integration fails early, verify the Issuer, redirect URI, and client registration before debugging tokens.
- If token validation fails in downstream APIs, compare the API's configured audience to the
audclaim actually issued by TokenIDP.