Advanced SCIM Provisioning

Map Luciq roles and app access during SCIM provisioning by creating custom attributes for the Luciq app in Okta, step by step.

To map roles and app access during SCIM provisioning, create custom attributes for the Luciq app in Okta.

Update app provisioning

Okta: Open provisioning settings

In Okta, go to Applications → Luciq → Provisioning.

Click Edit.

Okta: Enable attribute updates

In Okta, in Provisioning, enable Update User Attributes.

Set up Luciq custom attributes

Okta: Open the Luciq user profile

In Okta, go to Directory → Profile Editor.

Click Luciq User.

Okta: Add a custom attribute

In Okta, in Luciq User, click +Add mappings.

Okta: Create the role attribute

In Okta, in Luciq User, use these values:

Data type = string
Display name = Instabug Role
Variable name = instabugRole
External namespace = urn:ietf:params:scim:schemas:extension:instabug:2.0:User
Enable Enum.
Add the Instabug roles.
Choose the attribute type based on how you plan to use it:
- Personal: Each user is assigned their own value. Choose this if roles vary from user to user.
- Group: A single value is shared across a group of users. Choose this if you assign the same role to everyone in a group.

For the Admin role, use administrator as the value.

Okta: Create the application access attribute

In Okta, in Luciq User, use these values:

Data type = string array
Display name = Instabug Applications
Variable name = instabugApplications
External namespace = urn:ietf:params:scim:schemas:extension:instabug:2.0:User
Optional: Enable Enum.
Optional: Add your Luciq app names. Values must match exactly.
Choose the attribute type based on how you plan to use it:
- Personal: Each user is assigned their own app access. Choose this if app access varies from user to user.
- Group: A single set of apps is shared across a group of users. Choose this if you grant the same app access to everyone in a group.

By default, an app name grants access to all of that app's environments. To scope access to a single environment, use the format App:environment — for example, iOS App:Production grants access to the Production environment only, while iOS App grants access to all environments. The environment can be a built-in environment name (production, beta, staging, alpha, qa, or development) or the slug of a custom environment, including slugs that contain hyphens — for example, iOS App:pre-prod. Environment names are not case-sensitive, so iOS App:Production and iOS App:production are equivalent. The environment must be a real environment of that app; otherwise the whole value is treated as an app name. To grant more than one environment of the same app, add a separate value for each (for example, iOS App:Production and iOS App:Beta).

Configure attribute mapping

If you do not already have matching attributes on Okta User, create them first.

Okta: Add an attribute to Okta User

In Okta, go to Directory → Profile Editor → Okta User.

Click Add Attribute.

Okta: Add Instabug Role

In Okta, in Okta User, use these values:

Data type = string
Display name = Instabug Role
Variable name = instabugRole
Enable Enum.
Add the Instabug roles.

Okta: Add Instabug Applications

In Okta, in Okta User, use these values:

Data type = string array
Display name = Instabug Applications
Variable name = instabugApplications
Enable Enum.
Add your Luciq app names. Values must match exactly.

Map Okta User to Luciq User

Okta: Open Luciq mappings

In Okta, go to Applications → Luciq.

Click Edit Mappings.

Choose Okta User to Luciq.

Okta: Map the role attribute

In Okta, in Okta User to Luciq, select the Okta User attribute to map to Luciq.

From the dropdown, choose InstabugRole.

Your mapping should look like this.

Okta: Repeat for `InstabugApplications`

Repeat the same mapping for InstabugApplications.

Assign roles and app access to users

Okta: Start a new assignment

After setup, when you assign a new user for provisioning, Okta prompts you for role and app access.

These attributes are optional.

Okta: Open user assignment