OAuth 2.0 Authorization Code Grant

The Authorization Code Grant is used to request an authorization code that can be exchanged for an ID token and, typically, an access token. This grant is advantageous because tokens cannot be intercepted, as they are never exposed to the user agent (typically, a web browser). The flow is redirection-based, so the client needs to be able to interact with the resource owner’s user agent to initiate and complete the process.

Authorization Code Grant Flow

The diagram below provides an overview of the OAuth 2.0 Authorization Code Grant flow as implemented in EmpowerID. Each numbered step in the diagram corresponds to a key part of the process, which we explain in detail in the following section. This flow is essential for understanding how the client application interacts with the Authorization and Token Endpoints to authenticate users and obtain tokens securely.

Open

Detailed Steps of the Authorization Code Grant Flow

Now, let’s go through each step depicted in the diagram to understand how the OAuth 2.0 Authorization Code Grant flow works in detail:

1. Initiate Authorization Request: The client application initiates the flow by directing the resource owner’s user agent to the EmpowerID Authorization endpoint (https://<EID Server>/oauth/v2/ui/authorize) with the required parameters:

   • response_type: Specifies the desired type of response, which must be code to initiate the authorization code flow.

   • client_id: The identifier for the client application requesting access.

   • scope: A space-separated list of access permissions being requested (e.g., openid for OpenID Connect).

   • redirect_uri: Specifies where the user agent should be redirected after successful authentication.

   • Optional parameters, such as state (to prevent CSRF attacks) and nonce (to mitigate replay attacks), can also be included for enhanced security.

2. User Submits Credentials: The resource owner submits their credentials using a login form presented by the Authorization server. This may involve a traditional username-password combination, an external identity provider, or multi-factor authentication (MFA), depending on the security configuration.

3. Authorization Code Issued: Upon successful authentication, the Authorization server redirects the user agent to the specified redirect_uri, including an authorization code and, if applicable, an identity token (id_token) in the query parameters. This redirect keeps tokens hidden from the user agent and ensures a secure transmission back to the client application.

4. Token Request to Token Endpoint: The client application makes a back-channel request to the EmpowerID Token endpoint (https://<EID Server>/oauth/v2/token) to exchange the received authorization code for an access token and a refresh token. The request must include the following:

   • grant_type: Must be set to authorization_code.

   • client_id: The client application identifier.

   • client_secret: A secret key associated with the client application.

   • code: The authorization code obtained from Step 3.

   This request happens server-to-server, ensuring that sensitive information, such as the client_secret, remains secure.

5. Tokens Issued to Client Application: The Authorization server verifies the client credentials, validates the authorization code, and ensures the redirect_uri matches the one used in Step 1. If all checks pass, the Authorization server issues an access token (for accessing protected resources) and a refresh token (for obtaining a new access token without requiring further user authentication).

Authorization Code Grant

1. Initiate a login request to the EmpowerID Authorization endpoint, https://<EID Server>/oauth/v2/ui/authorize

2. Authenticate using username and password or any of the allowed external identity providers.

3. The Authorization server redirects to the redirect_uri with the response parameters in the query string.

4. Exchange the code for an access token by calling the EmpowerID Token endpoint, https://<EID Server>/oauth/v2/token

5. Returns access token and refresh token in the response.

Authorization Code Grant using .NET Client Library

1. Initialize ClientSettings by passing the client_id, client_secret, redirect_uri, token_endpoint, authorization_endpoint, tokeninfo_endpoint and userinfo_endpoint. Also, initialize a new AuthorizationCodeGrant by passing the clientSettings model.

2. Call the BuildAuthorizationRequestPacket() method to build authorization code flow parameters.

3. In the application’s callback method AuthorizationCodeGrantResponse() for example, extract the code and state, build an AuthorizationResponseModel model, and send it to the GetAccessToken() method.

Authorization Code Grant with PKCE (Proof Key for Code Exchange) Extension

1. Initiate a login request to the EmpowerID Authorization endpoint, https://<EID Server>/oauth/v2/ui/authorize

2. Authenticate using username and password or any of the allowed external identity providers.

3. Authorization server redirects to the redirect_uri with the response parameters in the query string.

4. Exchange the code for an access token by calling the EmpowerID Token endpoint, https://<EID Server>/oauth/v2/token

5. Returns access token and refresh token in the response.

Authorization Code Grant with PKCE Extension using .NET Client Library

1. Initialize ClientSettings by passing the client_id, client_secret, redirect_uri, token_endpoint, authorization_endpoint, tokeninfo_endpoint and userinfo_endpoint. Also, initialize a new AuthorizationCodeGrant by passing the clientSettings model.

2. Call the BuildAuthorizationRequestPacketWithPKCE() method to build the fully qualified URL to redirect to the authentication endpoint.

3. In the application’s callback method AuthorizationCodeGrantWithPKCE() for example, extract the code ,state and the generated code_verifier , build an AuthorizationResponseModel model and send it to the GetAccessToken() method.