Okta Custom Attributes Instructions

Modified on Tue, 11 Feb at 12:17 PM


Pre-requisites

1. Unique Location Attribute:

  • Identify a unique attribute to represent each location (e.g., City, ZIP Code, or State) and share it with your Visitly account manager.

  • This attribute will be mapped to Visitly’s Primary Location field for assigning employees to their correct locations.

2. Access to Okta:

  • Ensure you have administrative access to your Okta instance.

3. Latest Visitly Kiosk App


Set Up Okta Integration 

Follow the steps outlined in Visitly’s official  Okta Integration Guide until Step 5. This ensures that:

  • The Visitly app is properly added in Okta.

  • Provisioning settings are enabled.


Navigate to Attribute Mapping

1. Log in to Okta as an administrator.

2. Open the Visitly app in your Okta admin dashboard.



3. Go to the Provisioning tab.

4. Select Attribute Mapping.



5. Click on Profile Editor.

6. Click on the Add Attribute button to create custom attributes.



Add Custom Attributes

For each custom attribute, configure the following fields:

1. Title

  • Display Name: Title

  • Variable Name: scim2headerauth.title

  • External Name: title

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



2. Employee Number

  • Display Name: Employee Number

  • Variable Name: scim2headerauth.employeeNumber

  • External Name: employeeNumber

  • External Namespace: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User



3. Department

  • Display Name: Department

  • Variable Name: scim2headerauth.department

  • External Name: department

  • External Namespace: urn:ietf:params:scim:schemas:extension:enterprise:2.0:User



4. Work Phone

  • Display Name: Work Phone

  • Variable Name: scim2headerauth.workPhone

  • External Name: phoneNumbers.^[type=='work'].value

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



5. Mobile Phone

  • Display Name: Mobile Phone

  • Variable Name: scim2headerauth.mobilePhone

  • External Name: phoneNumbers.^[type=='mobile'].value

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



6. Primary Location

  • Display Name: Primary Location

  • Variable Name: scim2headerauth.defaultLocationName

  • External Name: defaultLocationName

  • External Namespace: urn:scim:schemas:extension:visitly:core:1.0:User



Map Attributes to Visitly

1. After creating the custom attributes, map them to Visitly fields in Okta.

2. For the Primary Location attribute:

  • Use the unique attribute (e.g., CityZIP Code, or State) that you shared with your Visitly account manager.

  • This ensures employees are assigned to the correct locations in Visitly.



3. Once all attributes are configured, click Save Attribute in Okta.

4. Test the integration by provisioning a test user to Visitly and confirming that the attributes (e.g., Title, Work Phone, Primary Location) are synced correctly.


Example Mapping for Primary Location

If you shared "City" as the unique attribute, it will map as follows:

  • Display Name: Primary Location

  • Variable Name: scim2headerauth.defaultLocationName

  • External Name: defaultLocationName

  • External Namespace: urn:scim:schemas:extension:visitly:core:1.0:User


This mapping ensures that the "City" field is synchronized as the Primary Location in Visitly.

Was this article helpful?

That’s Great!

Thank you for your feedback

Sorry! We couldn't be helpful

Thank you for your feedback

Let us know how can we improve this article!

Select at least one of the reasons

Feedback sent

We appreciate your effort and will try to fix the article