Import user attributes using custom mappings

Teams can port existing user attributes into Advanced Server Access from a pre-existing deployment. This is commonly used if the team wants to retain any user and group metadata as they migrate infrastructure to Advanced Server Access.

To import a configuration using custom mappings:

  1. Create custom attributes for your Okta user profile, adding one custom attribute for each supported user attribute. You can pick the attribute name, but set the data type for every attribute to string, except for Unix UID and Unix GID, which should be set to integer.
  2. Populate the Okta user profile attributes that you created. You can do this in many ways, including importing a comma-separated values (CSV) list of users, or setting up application-based mappings to your Okta user profile from the Provisioning tab of another application in the Okta Integration Network (OIN).
  3. Set up application-based mappings from your Okta user profile to Advanced Server Access. Make these changes from the Provisioning tab of the Advanced Server Access application, ensuring that the mappings are from Okta to Advanced Server Access. Assign mappings for the custom attributes that you created and save your changes.

Any users that have the custom attribute set in Okta Universal Directory will now automatically have that custom attribute provisioned when they are assigned to Advanced Server Access.