Token Management with Postman

You can manage your HPE Aruba Networking Central tokens using the Token Management collection within HPE Aruba Networking Central Postman Collection . These token management workflows have been simplified with the help of Postman Collection Runners.

📘

Postman Definition

The Collection Runner enables you to run the requests in a Postman Collection in a specified order to test the functionality of your API. The Collection Runner logs the test results for each request, and it can use scripts to pass data between requests and change the request workflow.

Create Token (Non-SSO Users)

🚧

Note

The steps mentioned below are valid only for non-SSO users. A non-SSO user is a local/system user that does not share the same domain name as SSO users.

SSO Users can create tokens from HPE Aruba Networking Central UI. Once created, they can add the access_token, refresh_token, client_ID and client_secret tokens in the HPE Aruba Networking Central ENV environment to make API calls to HPE Aruba Networking Central & refresh access tokens via Postman.

You can create access tokens using the Create Token's collection runner. You can follow the steps listed below to use the Create Token Collection runner to create access tokens:

1. Within your personal workspace, select the Environments tab and add values for the following variables in the HPE Aruba Networking Central ENV:

2. Once the valid values are set, save the environment, and set the HPE Aruba Networking Central ENV as the active environment for your workspace.
3. Click on the Collections tab and select HPE Aruba Networking Central collection. Within the collection, go to Create Token(Non SSO Users) collection in Token Management
4. Click on Run to open this collection's runner. You don't have to make any changes to run options.
5. Click on Run HPE Aruba Networking Central.

This collection runner will sequentially make the OAuth API calls required to create tokens. You can check with Postman console to see the status of the collection runner. If successful, the access token will be generated and the following variables will updated in HPE Aruba Networking Central ENV environment:

Refresh Token

Access token expires after a certain time. Refresh token API should be used to refresh the tokens before and after they expire. You can follow the below steps to use the Refresh Token collection runner to refresh access tokens:

1. Within your personal workspace, select the Environments tab and add values for the following variables in the HPE Aruba Networking Central ENV:

2. Once the valid values are set, save the environment, and set the HPE Aruba Networking Central ENV as the active environment for your workspace.
3. Click on the Collections tab and select HPE Aruba Networking Central collection. Within the collection, go to Refresh Token collection in Token Management.
4. Click on Run to open this collection's runner. You don't have to make any changes to run options.
5. Click on Run HPE Aruba Networking Central.

This collection runner will make the Refresh API call. You can check with Postman console to see the status of the collection runner. If successful, the access_token and refresh_token will be refreshed and updated in HPE Aruba Networking Central ENV environment.

Delete Token (Non-SSO Users)

Once you no longer need an access token, you can use the Delete API to revoke the access token. This API call only be used for access tokens that were generated via OAuth APIs. You can follow the below steps to use the Delete Token collection runner to delete access tokens:

1. Within your personal workspace, select the Environments tab and add values for the following variables in the HPE Aruba Networking Central ENV:

2. Once the valid values are set, save the environment, and set the HPE Aruba Networking Central ENV as the active environment for your workspace.
3. Click on the Collections tab and select HPE Aruba Networking Central collection. Within the collection, go to Delete Token (Non SSO Users) collection in Token Management.
4. Click on Run to open this collection's runner. You don't have to make any changes to run options.
5. Click on Run HPE Aruba Networking Central.

This collection runner will make the Delete API call. You can check with Postman console to see the status of the collection runner. If successfully, the access token will be revoked and the following variables will be removed from HPE Aruba Networking Central ENV environment: access_token, refresh_token csrf_token, session_token