Use personal access tokens to authenticate service users for machine-to-machine interactions.
To create a personal access token:
Sign in to the Identity and Access Management web application in Provider Connectivity Assurance.
If DNS is available, access the web application at
https://auth.<deployment URL>.
If DNS is unavailable, use the IP address of the Provider Connectivity Assurance deployment tenant andport 3443.https://<IP address>:3443 // For deployments without DNS https://auth.<deployment URL> // For deployments with DNSSet the organization to the Provider Connectivity Assurance tenant.
Use the organization drop-down list (upper-left) to find your specific tenant name.
Note: The name
pcamay have been used for the tenant during installation, or a different name may have been chosen by the installer.Create a service user.
Choose Users > Service Users.
Click + New.

Enter the required fields.
In User Name, we recommend to use the
<username>@<tenant_name>format. For example,integrationUser@pca.In the Access Token Type drop-down list, select Bearer.
Click Create.
Assign the an appropriate role to the service user. For more details on roles, see User Management.
In the left-side navigation, choose Authorizations and then click + New.

In Search for a project, choose Analytics and then click Continue.

Select the checkbox for your desired role. Take note of the following mapping of Role names in the Identity and Access Management backend service vs in the Analytics UI:
Analytics Role Name
IAM Role Name
Admin
tenant-admin
User
tenant-user
Contributor
tenant-contributor
Portal
tenant-portal

Click Save.
Generate a new personal access token with an appropriate expiration date.
In the left-side navigation, choose Personal Access Tokens and then click + New.
Select an expiration date, and then click Add.
The personal access token appears.
Note: You must regenerate the token and update it before it expires. Use an expiration date that aligns with your organization’s processes.
Copy and securely store this personal access token to the machine that requires it as you will not be able to retrieve it again.
© 2026 Cisco and/or its affiliates. All rights reserved.
For more information about trademarks, please visit: Cisco trademarks
For more information about legal terms, please visit: Cisco legal terms