Destination Configuration for Okta Importer
Jira Connection Configuration
Our application leverages Jira Rest API for programmatic access while updating Object Schema, Object Type, and Attribute configurations of JSM Assets.
Navigate to Destination Tab and select “+” button.
By Default the connection will be set to Current Site, if you wish to set up and External Site connection, please follow the steps here.
|
Select “Add” to save changes.
|
Schema Selection Configuration
You have two options in this section:
Create a new Object Schema
Use an existing Object Schema
Pro tip: We recommend creating a new Object Schema to store Okta related data separately. his allows you to assign roles only to necessary users or groups. Since the imported data includes personal information, ensure compliance with your organization’s data policies.
Option 1: Create a New Object Schema
Once Destination Connection is successfully created, click the Set/Select button. The option to create a new object schema is set by default.
Fill in the following fields:
Object Schema Name: Okta
Object Schema Key: OKT
Description: Auto-generated Okta data.
Then, click "Create Object Schema" to proceed.
|
Please Note: The links to the new schema will be shown above the configuration, just below the Schema Selection Configuration Heading.
Troubleshooting Connection Issues
If you don’t receive a success message, check the following:
User Permissions: Ensure the user is a Jira Admin and has a JSM User license.
Site Allow List: If an IP allow list is enabled, add the Forge IP addresses to grant access to your site through our application.
Option 2: Use an Existing Object Schema
Select an Existing Object Schema and locate the schema you wish to utilize.
Click "Use Existing Object Schema" to continue.
If the selected schema already contains the same Object Types, you will be notified and required to update them before moving forward.
Pro tip: Either you chose Option 1 or 2, make sure that you remove the default values from the Object Schema Roles menu. It should look like the following.
Then, only add the relevant users, groups, or apps.
Import Token Configuration
To import a large amount of data into JSM Assets, you need to generate a key that securely authorizes the data transfer (more info).
Please add the Import Token for your External Import configuration in Assets.
Once Schema is created/selected, you can click on the Object Schema, which will reveal the Links to the schema:
|
Click on the Import Tab link to navigate directly to the Import Section within your Schema in Assets. Select “Create Import” to begin the token creation process.
|
Select "External Import" and click "Next".
Enter a Name and Description.
|
Click the three dots (…) and select "Generate new token".
|
Copy the generated token.
Return back to Destination. Click Set button and paste the token into the Import Token field then click "Save & Check".
|
Now, it is time to Import.