Trouble Viewing Images? Right-click on any image and select "Open in new tab" to view a larger version. You can also zoom in using Ctrl + Mouse Wheel for easier readability.
Article Goal
Learn how to create an Okta API Token for use in WebReports authentication and integration.
Why Create a WebReports Okta API Token?
Creating an Okta API token allows WebReports to authenticate users and perform secure operations through the Okta API. This token serves as a bridge between WebReports and Okta's identity management services.
Important Tip: You will only see the token once during creation. Be sure to copy and store it in a secure location immediately after it's generated.
Where Do You Create the Okta API Token?
You can generate your Okta API Token by accessing the API section under Security in your Okta Developer Console.
Steps to Create Your Okta API Token
Step 1: Log in to Okta
Log in to your Okta Developer Account using your administrator credentials.
Step 2: Access the API Section
Expand the Security tab in the left-hand navigation pane and click API.
Step 3: Go to the Tokens Tab
Click on the Tokens tab, then select Create Token.
Step 4: Name Your Token
Enter a descriptive name for your token (e.g., WebReports Integration), and then click Create Token.
Step 5: Copy the Token Value
Key Step: After the token is successfully created, copy the Token Value immediately.
There is no way to retrieve it later if missed.
Important: Paste and store your token securely in a password manager or secure notes vault.
Next Steps
To continue setup, proceed to Step 3 in the Step-by-Step: Okta Authentication article for integrating the token with WebReports.
Article Summary
Creating a WebReports Okta API token enables secure authentication and integration with Okta identity services. After logging into your Okta developer portal, the token is created from the API > Tokens section and should be stored securely, as it cannot be retrieved again. This token is essential for connecting WebReports to Okta’s secure user authentication system and is referenced in later configuration steps during WebReports setup.
Comments
0 comments
Please sign in to leave a comment.