Configure the CSV directory integration profile attributes

  1. In the Admin Console, go to DirectoryProfile Editor.
  2. Find your CSV application and select Mappings.
  3. Map the CSV application's user profile attributes to user attributes in the Okta user profile. For an import to be successful, the following fields are mandatory. These default properties are created during app activation or reactivation if they don't exist.
    • login
    • firstName
    • lastName
    • email

    You can also use the following default mappings by entering them as your headers within the CSV file (CSV app user => Okta user). These attribute headers are case-sensitive.

    • userName => login
    • firstName => firstName
    • lastName => lastName
    • email => email

    As an admin, you can update the attributes you want to map by using the Okta Expression Language.

  4. Optional. Use the profile editor to map alternative attributes from your CSV file instead of using the Okta default attributes, or you can import other fields as custom attributes. In either case, complete these steps:
    1. Find your CSV application in the Profile Editor page and select Profile.
    2. Select Add Attribute, add the new attribute, and save.
    3. Select Map Attributes, and map the new attribute, which will replace the Okta default.
    4. You can delete the Okta default attribute.
    5. Save your changes.

      The new attribute appears under FiltersCustom.

      Okta queries the name that you specify when determining which headers in the CSV file correspond to the attribute.
    • Okta only supports non-array attributes (that is, string, boolean, integer, number).
    • Mapping a unique identifier from the CSV file isn't required. If you would prefer that the unique identifier be populated on the user profile, access the mappings and configure it there.
    • If there are other attributes you want to import from the CSV file, they must be added to your schema. If your CSV file has attributes or headers that aren't configured within your user profile, Okta ignores them and their associated values for each user.
    • If a CSV column isn't included as an attribute in a CSV user profile, the data from that column is ignored. For example, if you've configured userName, firstName, lastName, email, and employeeId within the profile editor, but your CSV includes an additional attribute with the Address header, Okta won't import Address or any values populated for a user with an address.
    • Plain text password migration isn't supported.