MaestroQA/Okta SCIM configuration guide

Configuration guide for Okta with SCIM provisioning on MaestroQA

Harrison Hunter avatar
Written by Harrison Hunter
Updated over a week ago


MaestroQA’s SCIM enabled okta integration supports the following features:

  • Create users: Users in Okta that are assigned to the MaestroQA application in Okta are automatically added as agents to your Account in MaestroQA

  • Update user attributes: Updates to a user’s name can be pushed down to the MaestroQA application. This functionality can also be used to reactivate a deactivated user

  • Deactivate users: Users that are deactivated in Okta will be automatically deactivated in the MaestroQA application. While okta does not support removing users, you can remove users entirely within the MaestroQA app.

At Present, MaestroQA does not support the following Okta provisioning features via SCIM, but may in the future:

  • Push Groups

  • Import Groups

  • Import Users

  • Sync password

  • Enhanced group push

This is a one-way integration, with our SCIM app you can provision new users present in Okta in the MaestroQA app.


In order to leverage this Integration, you must have Single Sign On with Okta setup for your Organization. Please contact your success manager or support via the in-app chat if you would like to implement Okta for your MaestroQA account

Step ­by ­Step Configuration

  1. Generate an API Token on See Section: Authentication - Obtaining API Token on our help guide

  2. Click on the “Sign On” tab in the application. Click on Edit in the top right corner

  3. Under the “Credentials Details” Section make sure that:

    1. Application username format: Email

    2. Update application username on: Create and update

    3. Save

credentials details

4. Click on the “Provisioning” tab in the application. Under the “Settings” panel on the left side, click the “Integration” link. Then click the “Configure API Integration” button

  • Check Enable API Integration

  • Username: apikey

  • Password: <Enter API token Generated in Step 1>

  • Once the api token is entered, click on the <Test Connector Configuration> Button to check API authentication. You will see the below message, once tested, Click on Save.

verification success

5. After saving, there will be 2 more options in the settings menu. In the left menu, Select “To App” in the settings panel. Click on Edit in the top right corner, and check the enable box for the following actions:

  1. Create Users

  2. Update User Attributes

  3. Deactivate Users

Click Save

okta maestroqa

Configuration is now complete. Okta can now Provision Users in the MaestroQA app, and push updates

Setting up Custom Profile Attributes in Okta with SCIM

  1. Navigate to the Provisioning Tab for the MaestroQA SAML App. Make sure you are on “To App” in the left hand menu. Scroll down to ”Go to Profile Editor” and select.

2. Click on Add Attribute button

3. Begin to Add Custom Attributes in here as follows

  • Set Display Name and Variable Name as pertaining to value

  • The External Name should be prepended with profile ex. profile.location where location is the variable name.

  • External Namespace is: urn:ietf:params:scim:schemas:core:2.0:User

  • Scope: User Personal must be checked

  • Save ( or Save and Add another if adding multiple)

4. After Adding your Custom Attributes. Click on Mappings

5. In the Mappings editor, please select the Okta to MaestroQA Window (we do not support importing data from MaestroQA into Okta, this is a one way integration where Okta sends user data to Maestroqa)

For each new Attribute created, select the appropriate User values to be mapped into Okta (in the below example we are mapping the CostCenter to the newly created attribute1. With these edits, Okta will push any CostCenter user attributes to MaestroQA inside the profile.Attribute1 key via SCIM)

6. Click on Save Mappings

Learn how you can use these profile attributes to create automated agent and user groups by reading this article.

Schema Discovery

For more information on our implementation of the SCIM API: Please visit this help article

Troubleshooting and Tips

At this time, we do not support Username and Email updates. The MaestroQA application sets the user's email address ( as specified in the profile) as the username to log in to MaestroQA. We do not currently support setting an email in the username that does not match the user’s email.

Changes in user attributes in Okta will be immediately pushed to MaestroQA.

If you have questions or difficulties with your MaestroQA/Okta SCIM integration, please contact your Success Manager via email, or our support team via the In-app Chat.

Did this answer your question?