0
How Client Credentials Grant Works

Unlike user-centric flows that require an authorization code dance, the client credentials grant is a streamlined, single-legged protocol:

  1. Autonomous Machine Authentication: The background service operates under its own identity rather than delegating on behalf of an end user. There are no login prompts, MFA gates, or browser redirects.
  2. Direct HTTP POST to Token Endpoint: The client sends a single POST to the IdP's token endpoint with grant_type=client_credentials, client_id, client_secret, and the desired scope.
  3. Credential & Permission Verification: The IdP verifies the client secret and inspects which application roles or API scopes have been granted to this client registration by a directory administrator.
  4. Access Token Issuance: The IdP returns an HTTP 200 containing an access_token (typically valid for 1 hour).
  5. Why There is No ID Token or Refresh Token: An id_token asserts the identity of a human who logged in; because no user is present, an ID token is not issued. Similarly, refresh tokens are not provided because the machine client can simply request a fresh access token whenever needed using its stored secret.
1
Application Configuration

Enter your machine client credentials. No redirect URI or user interaction is required.

The IdP OAuth 2.0 token URL where the client presents its credentials.
The unique application ID assigned by your identity provider.
The application secret. Transmitted only to our backend proxy and never stored.
Specifies the resource or permissions requested (e.g. https://graph.microsoft.com/.default for Entra ID).
2
Token Request Preview

This is the raw HTTP POST that will be sent to the token endpoint. Notice the form-urlencoded parameters proving the application's identity.

POSTToken Endpoint
// Fill in config above to preview
3
Exact Request Sent by Backend

The backend confirms the exact HTTP POST headers and body sent over the wire to the IdP.

// Will appear after executing the request
4
IdP Token Response

The IdP returns a JSON payload containing the access_token, its token type (Bearer), and lifetime in seconds (expires_in).

// Awaiting request…
5
Token Decoding & Claims Inspection

Explore the claims inside the access token. Notice that the sub (subject) refers to the client application itself, and the roles claim reflects the application permissions approved by the tenant admin.

// Decoded tokens will appear here after request execution