Playground

The agent calls the mock MCP server with no token. It answers 401 with a WWW-Authenticate header whose resource_metadata points to its Protected Resource Metadata.

The agent fetches /.well-known/oauth-protected-resource (RFC 9728). The authorization_servers entry is the per-Resource AIGW authorization server you configured.

The agent fetches the real /.well-known/openid-configuration from AIGW. It learns the per-Resource authorization endpoint, the core token endpoint, the registration endpoint and the supported scopes, which include the Resource's own scopes.

The agent registers at POST /api/register. AIGW returns 201 with a new client_id and client_secret, the domain it derived from the redirect URI, and a verification_method of none, because the Playground doesn't sign requests with Web Bot Auth.

The request deliberately sends no scope. AIGW rejects a registration outright if any requested scope isn't registrable for a dynamic client, so scopes are chosen in the next step.

Pick which discovered scopes to request, then press Continue to AIGW login. The Playground builds an Authorization Code with PKCE (S256) request to the per-Resource authorization endpoint and sends your browser there.

You sign in on the real AIGW page with the identity providers the Resource allows and approve the consent screen. Back in the Playground, the step shows the 302 redirect with the returned code and state. If authorization is refused right after registration, the agent may be Pending or Rejected under the Project's agent policy.

The agent exchanges the code, its client_secret and the PKCE code_verifier at the core token endpoint. The response is the unmodified AIGW result: access_token, id_token, refresh_token and the granted scope. The Playground decodes both JWTs. In the access token, look at these claims:

Now the Playground plays the MCP server. It authenticates to AIGW with the Proxy client ID and secret (grant_type=client_credentials) and receives a Proxy token.

The MCP server calls the credential redemption endpoint with the user's AIGW token and the Proxy token.

POST https://api.aigw.eval.loginid.ai/api/credentials/tokenAuthorization: Bearer <user's AIGW access token>X-Proxy-Token: <Proxy token>Content-Type: application/json{"resource": "<resource indicator>"}

AIGW returns the merchant access token it obtained from the merchant's authorization server during sign-in, in access_token, with expires_at and scopes when present. Decode it and you'll see a token issued by the merchant's authorization server (Keycloak in the default Playground Resource), not by AIGW. The full response is in the redemption reference.

The MCP server calls the mock Resource API with the merchant token. The flow is complete.