zdlake.com. Client registration, token exchange, revocation, and the MCP resource remain on api.zdlake.com.
When to use OAuth vs API keys
Discovery
MCP clients discover Zero’s OAuth configuration automatically through well-known metadata endpoints.Protected resource metadata
Authorization server metadata
WWW-Authenticate header
Unauthenticated MCP requests return:Client registration
Zero supports dynamic client registration for public MCP clients.Authorization code flow with PKCE
Step 1: Authorization
Step 2: Token exchange
Step 3: Use the access token
Step 4: Refresh
Step 5: Revoke
200 OK even when the token was already revoked or is unknown.
Scope
Data model
Platform compatibility
Security
- Access, refresh, and authorization codes are stored as SHA-256 hashes, never plaintext.
- Access tokens expire after one hour.
- Refresh tokens expire after 30 days and rotate on use.
- PKCE S256 is required for every authorization request.
- Authorization codes expire after 10 minutes and can be consumed once.
- Tokens are bound to one client, user, organization, scope, and MCP resource.
- MCP access tokens are validated at the MCP boundary and are not forwarded to the REST API.