Discovery & Onboarding Gates


MCP Server & UI Tiers

OAuth 2.1, PKCE (S256), CIMD & Persistent Account Linking

This workbench exercises the complete OAuth 2.1 identity lifecycle defined in openapi/producer-openapi.yaml, including Google Account Linking redirect URI allowlisting, RFC 7591 Dynamic Client Registration, IETF Client ID Metadata Documents (CIMD) with private_key_jwt, RFC 7636 PKCE (S256), and Persistent Linking (non-rotating refresh tokens).

Persistent Linking Requirement for Refresh Tokens

When refreshing access tokens via POST /oauth/token (grant_type=refresh_token), partner authorization servers should preserve the existing refresh_token validity across refreshes (Persistent Linking) rather than invalidating the refresh token on single use without a grace window. Use Step 4 below (or send header X-Simulate-Token-Rotation: true) to compare Persistent Linking against destructive single-use rotation.

Interactive OAuth 2.1 Lifecycle Steps

1. Redirect URI Allowlist & RFC 7591 Dynamic Client Registration (POST /oauth/register)

Verify that your OAuth server allowlists the production, sandbox, and test redirect URIs for service ID , and dynamically register an OAuth 2.1 client via registerOAuthClient (POST /oauth/register).

{
  "client_name": "Connected Apps Reference Consumer",
  "redirect_uris": [
    "https://oauth-redirect.googleusercontent.com/r/",
    "https://oauth-redirect-sandbox.googleusercontent.com/r/",
    "https://oauth-redirect-test.googleusercontent.com/r/"
  ]
}

2. PKCE (S256) Generator & Authorization Code Issuance (/oauth/authorize)

Generate a cryptographic RFC 7636 code_verifier and S256 code_challenge (BASE64URL(SHA256(code_verifier))), then request a single-use authorization code from authorizeOAuthClient (GET /oauth/authorize) for client connected-apps-sample-client.

3. Token Exchange & CIMD private_key_jwt Verification (POST /oauth/token)

Exchange the authorization code and code_verifier at exchangeOAuthToken (POST /oauth/token), or test Use Case 2B (CIMD private_key_jwt) where the Producer resolves the Consumer's /.well-known/oauth-client.json (getClientMetadataDocument) and /.well-known/jwks.json (getConsumerJwks) using the spec-driven Consumer OpenAPI client.

4. Persistent Linking vs. Destructive Refresh Token Rotation

Execute grant_type=refresh_token calls against POST /oauth/token. By default, the server preserves the same refresh_token across refreshes (Persistent Linking). Toggle X-Simulate-Token-Rotation: true to simulate single-use token rotation and observe how a subsequent retry with the original refresh token fails with invalid_grant.