Okta Provisioning to Sigma on AWS Fails With an Unauthorized Error
Last Updated:
Okta Integration Network
All Engines
Okta Classic Engine
Okta Identity Engine
Overview
The provisioning flow for Sigma on AWS fails in Okta due to an invalid API token. Resolve this by updating the API token in the application integration settings and retrying the failed tasks. When this issue occurs, Okta displays the following error message in the dashboard:
Automatic provisioning of user <username> to app Sigma on AWS failed: Error while verifying if user <username> exists: Unauthorized. Errors reported by remote server
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Application Programming Interface (API)
- Sigma on AWS
- Provisioning
Cause
The API token used for creating the API connection is invalid.
Solution
How is the invalid API token resolved for Sigma on AWS?
Update the API token in the application integration settings and retry the failed provisioning tasks by following these steps.
- Navigate to the Okta Admin Console.
- Go to Applications > Applications and select Sigma on AWS.
- Navigate to the Provisioning tab and select Integration.
- Choose Edit.
- Enter the Bearer Token received when setting up provisioning in the Sigma Admin Portal in the API Token field.
- Select Test API Credentials to verify the connection is successful.
- Choose Save.
- Navigate to Dashboard > Tasks.
- Locate the failed task for the user and select Retry Selected.
