Scribd
Upload
13 views12 pages

Generate A UUID or JWT Access Token

The document outlines the steps to configure two clients, ClientA and ClientB, in the OAuth Manager, specifying their required access_token_type parameters. ClientA is set to generate a UUID token while ClientB is configured to generate a JWT token, with specific instructions for each client. Additionally, it details the process for importing a policy in the Policy Manager and making necessary global settings adjustments.

Uploaded by

Anonymous dRxI7Qi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
13 views12 pages

Generate A UUID or JWT Access Token

The document outlines the steps to configure two clients, ClientA and ClientB, in the OAuth Manager, specifying their required access_token_type parameters. ClientA is set to generate a UUID token while ClientB is configured to generate a JWT token, with specific instructions for each client. Additionally, it details the process for importing a policy in the Policy Manager and making necessary global settings adjustments.

Uploaded by

Anonymous dRxI7Qi
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

In the OAuth Manager, there are two new clients:

 Click [Edit] for ClientA


 In the Custom Field, add {“access_token_type”:”UUID”}
 Click [Update Client]

 NOTE: The access_token_type parameter is required. You can set


this parameter to an desired value but it cannot be an empty
value.

{“access_token_type”:”abc”} YES

{“access_token_type”:””} NO
 Click the [Edit] for Client B
 In the Custom Field, add {“access_token_type”:”JWT”}
 Click [Update Client]

 NOTE: The access_token_type parameter is required. It MUST be


set to JWT and it is case sensitive.
The access_token_type parameter has been set for each client:

NOTE: This parameter can be set for pre-existing clients. If you do not set this parameter, the client will always generate a
JWT access token.
 Log in to the Policy Manager as an admin user
 In the lower search bar, on the left-hand side, look for the #OTK Generate JWT OAuth Token policy
 Click [Import Policy]
 Select the downloaded [Link]
 Click [Save and Activate]
*** This part is optional and not required ***

 Right-click on the #OTK Generate JWT OAuth Token policy


 Click on Revision History
 Click [Set Comment] and add a comment about the customized policy
 Go to Tasks > Global Settings > Manage cluster-Wide Properties
 Make sure that the otk.access_token.enable_jwt CWP has been added and set to true
 From Postman (or another client), go to the Authorization Tab
 From the dropdown, select Basic Auth
 Add the client ID as the username, then add the client secret as the password

ClientA’s client ID + client secret

 Click the Body tab


 Select the x-www-form-urlencoded radio button
 Add the grant_type, username, and password
 The username/password credentials should be able to
log in to the Policy Manager
 Change the HTTP method to POST
 Add the URL to the endpoint as [Link]
 Click [Send]

Client A will generate a UUID token


 Go back to the Authorization Tab
 Change the client ID and client secret
 Do not change any information on the Body tab

ClientB’s client ID + client secret


 Click [Send]

ClientB will generate a JWT

You might also like