- Created by Phillip Hanegan, last modified on Jul 13, 2021
You are viewing an old version of this page. View the current version.
Compare with Current View Page History
« Previous Version 2 Next »
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 in that 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.
The sequence for this flow is as follows:
The client application initiates the flow by directing the resource owner’s user agent to the EmpowerID Authorization endpoint with the required parameters. These parameters include a response type, client identifier, scope, and a redirect URL that specifies where to send the user agent after the resource owner authenticates.
The resource owner submits credentials.
Upon successful authentication, the Authorization sever sends an authorization code and identity token to the specified redirect URL.
The client application calls the EmpowerID Token endpoint to exchange the authorization code for an access token and a refresh token.
The Authorization server authenticates the client application by verifying the Client ID and Client Secret, validates the authorization code, checks the redirect URL and issues the access and refresh tokens.
You can download sample .NET framework code at https://dl1.empowerid.com/files/OAuthTestSamplecode.zip
Authorization Code Grant
1. Initiate a login request to the EmpowerID Authorization endpoint, https://<EID Server>/oauth/v2/ui/authorize
https://<EID Server>/oauth/v2/ui/authorize ?client_id=xxxxxxxxxxxxxxxxxx &redirect_uri=https%3A%2F%2Ftestoauthapp.com%2FcallbackUrl &response_type=code &scope=openid &state=xxxxxxxxxxxxxxxxxx &nonce=xxxxxxxxxxxxxxxxxx
Request Parameter | Required/Optional | Description |
---|---|---|
| required | Must be |
| required | Must be the EmpowerID OAuth application client identifier. |
| required | The client app URL to which the authorization server will redirect after request approval. This URL should be registered in the Callback URLs on the EmpowerID OAuth application. |
| required | A space-separated list of strings that the user consents to. Values include |
| optional | A random string value sent by the client to maintain session and prevent CSR attacks |
| optional | A random string value sent by client to uniquely identify each request |
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.
https://testoauthapp.com/callbackUrl ?state=xxxxxxxxxxxxxxxxxx &code= xxxxxxxxxxxxxxxxxx &id_token= xxxxxxxxxxxxxxxxxx
Response Parameter | Description |
---|---|
| The value sent by the client to maintain the session |
| The authorization code generated by the authorization server |
| The identity token issued by the authorization server for OpenID Connect flow |
4. Exchange the code for an access token by calling the EmpowerID Token endpoint, https://<EID Server>/oauth/v2/token
https://<EID Server>/oauth/v2/token ?client_id={The Client ID of the OAuth app you registered in EmpowerID} &client_secret={The Client Secret of the OAuth app you registered in EmpowerID} &grant_type=authorization_code &code=xxxxxxxxxxxxxxxxxx
Request Parameter | Required/Optional | Description |
---|---|---|
| required | Must be |
| required | Must be the EmpowerID OAuth application client identifier. |
| required | Must be the EmpowerID OAuth application client secret. |
| required | The authorization code received from the authorization server |
5. Returns access token and refresh token in the response.
{ "access_token": "xxxxxxxxxxxxxxxxxxxxxx", "token_type": "Bearer", "expires_in": 3600, "refresh_token": "xxxxxxxxxxxxxxxxxxxxxx", "id_token": "xxxxxxxxxxxxxxxxxxxxxx", "id": "xxxxxxxxxxxxxxxxxxxxxx" }
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.
var clientSettings = new ClientSettings( “client_id”, “client_secret”, “redirect_uri”, “https://<EID Server>/oauth/v2/token”, “https://<EID Server>/oauth/v2/ui/authorize”, “https://<EID Server>/oauth/v2/tokeninfo”, “https://<EID Server>/oauth/v2/userinfo”); var handler = new AuthorizationCodeGrant(clientSettings);
2. Call the BuildAuthorizationRequestPacket()
method to build authorization code flow parameters.
//Generate random nonce and state var nonce = Guid.NewGuid().ToString("N"); var state = Guid.NewGuid().ToString("N"); //Use the below code for "code" flow to build parameters var parameters = handler.BuildAuthorizationRequestPacket (ParameterFormat.FormUrlEncoded, state, null, nonce, null); //Use the below code for "code id_token" flow to build parameters var responseTypes = new List<ResponseType> { ResponseType.id_token }; var parameters = handler.BuildAuthorizationRequestPacket (ParameterFormat.FormUrlEncoded, state, "openid", nonce, responseTypes); //Generate redirect URL var redirectUrl = string.Format("{0}?{1}", clientSettings.AuthorizeUrl, 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.
public ActionResult AuthorizationCodeGrantResponse(AuthorizationResponseModel model) { AuthorizationResponseModel authorizationResponseModel = new AuthorizationResponseModel() {Code = "xxxxxxx", State = state}; AccessTokenResponseModel tokenResponseModel = null; try { tokenResponseModel = handler.GetAccessToken<AccessTokenResponseModel>( RequestMethod.POST, ParameterFormat.FormUrlEncoded, authorizationResponseModel, false); } catch { //Handle error } }
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
https://<EID Server>/oauth/v2/ui/authorize ?client_id=xxxxxxxxxxxxxxxxxx &redirect_uri=https%3A%2F%2Ftestoauthapp.com%2FcallbackUrl &response_type=code &state=xxxxxxxxxxxxxxxxxx &nonce=xxxxxxxxxxxxxxxxxx &scope=openid &code_challenge=xxxxxxxxxxxxxxxxxx &code_challenge_method=S256
Request Parameter | Required/Optional | Description |
---|---|---|
| required | Must be |
| required | Must be the EmpowerID OAuth application client identifier. |
| required | The client app URL to which the authorization server will redirect after request approval. This URL should be registered in the Callback URLs on the EmpowerID OAuth application. |
| required | A space-separated list of strings that the user consents to. Values include |
| recommended | Specifies the transformation method used for the
Defaults to |
| required | The string derived from the
Please refer to the PKCE RFC for generating the Code Verifier. |
| optional | A random string value sent by the client to maintain session and prevent CSR attacks |
| optional | A random string value sent by client to uniquely identify each request |
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.
https://testoauthapp.com/callbackUrl ?state=xxxxxxxxxxxxxxxxxx &code= xxxxxxxxxxxxxxxxxx &id_token= xxxxxxxxxxxxxxxxxx
Response Parameter | Description |
---|---|
| The value sent by the client to maintain the session |
| The authorization code generated by the authorization server |
| The identity token issued by the authorization server for OpenID Connect flow |
4. Exchange the code for an access token by calling the EmpowerID Token endpoint, https://<EID Server>/oauth/v2/token
https://<EID Server>/oauth/v2/token ?client_id={The Client ID of the OAuth app you registered in EmpowerID} &client_secret={The Client Secret of the OAuth app you registered in EmpowerID} &grant_type=authorization_code &code=xxxxxxxxxxxxxxxxxx &code_verifier=xxxxxxxxxxxxxxxxxx
Request Parameter | Required/Optional | Description |
---|---|---|
| required | Must be |
| required | Must be the EmpowerID OAuth application client identifier. |
| required | Must be the EmpowerID OAuth application client secret. |
| required | The authorization code received from the authorization server |
| required | The Code Verifier value generated by the client during the initial authorization request |
5. Returns access token and refresh token in the response.
{ "access_token": "xxxxxxxxxxxxxxxxxxxxxx", "token_type": "Bearer", "expires_in": 3600, "refresh_token": "xxxxxxxxxxxxxxxxxxxxxx", "id_token": "xxxxxxxxxxxxxxxxxxxxxx", "id": "xxxxxxxxxxxxxxxxxxxxxx" }
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.
var clientSettings = new ClientSettings( “client_id”, “client_secret”, “redirect_uri”, “https://<EID Server>/oauth/v2/token”, “https://<EID Server>/oauth/v2/ui/authorize”, “https://<EID Server>/oauth/v2/tokeninfo”, “https://<EID Server>/oauth/v2/userinfo”); var handler = new AuthorizationCodeGrant(clientSettings);
2. Call the BuildAuthorizationRequestPacketWithPKCE()
method to build the fully qualified URL to redirect to the authentication endpoint.
//Generate random nonce and state var nonce = Guid.NewGuid().ToString("N"); var state = Guid.NewGuid().ToString("N"); //Generate code_verifier var unreservedChars = "ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz0123456789.-_`"; Random random = new Random(); var code_verifier = new string(Enumerable.Repeat(unreservedChars, 43).Select(s => s[random.Next(s.Length)]).ToArray()); //Store the generated code_verifier in cookie for example CookieHelper.SetCookieData("OAuthCodeVerifier", code_verifier); //Generate code_challenge (if plain) //var code_challenge = code_verifier; //var code_challenge_method = "plain"; //Generate code_challenge (if S256) var bytes = new SHA256CryptoServiceProvider().ComputeHash(Encoding.ASCII.GetBytes(code_verifier)); var code_challenge = Convert.ToBase64String(bytes).Split('=')[0].Replace('+', '-').Replace('/', '_'); var code_challenge_method = "S256"; //Use the below code for "code" flow to build parameters var parameters = handler.BuildAuthorizationRequestPacketWithPKCE (ParameterFormat.FormUrlEncoded, state, null, nonce, code_challenge, code_challenge_method, null); //Use the below code for "code id_token" flow to build parameters //var responseTypes = new List<ResponseType> { ResponseType.id_token }; //var parameters = handler.BuildAuthorizationRequestPacketWithPKCE //(ParameterFormat.FormUrlEncoded, state, "openid", nonce, code_challenge, code_challenge_method, responseTypes); //Generate redirect URL var redirectUrl = string.Format("{0}?{1}", clientSettings.AuthorizeUrl, parameters);
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.
public ActionResult AuthorizationCodeGrantWithPKCE(AuthorizationCodeGrantViewModel model) { AuthorizationResponseModel authorizationResponseModel = new AuthorizationResponseModel() {Code = "xxxxxxx", State = state}; //Retrieve the code_verifier stored in the cookie var code_verifier = CookieHelper.GetCookieData("OAuthCodeVerifier"); var additionalParams = new Dictionary<string, string>(); additionalParams["code_verifier"] = code_verifier; AccessTokenResponseModel tokenResponseModel = null; try { tokenResponseModel = handler.GetAccessToken<AccessTokenResponseModel>( RequestMethod.POST, ParameterFormat.FormUrlEncoded, authorizationResponseModel, false, null, additionalParams); } catch { //Handle error } }
IN THIS ARTICLE
- No labels