Mapping Location Attribute from Profile Source to Locale Attribute in Okta Profile Results in Null Value
Last Updated:
Overview
Mapping a location attribute from a profile source to the locale attribute in an Okta profile fails when the source attribute uses an improper format. During configuration, mapping the improperly formatted attribute results in a null value for the locale property. Administrators must convert the source attribute format to match the required locale format or create a custom attribute to store the original value.
Applies To
- Okta User Profile
- Locale Attribute
- Attribute Mapping
Cause
Mapping the location attribute to the locale attribute returns a null value because the location attribute is not in the proper format. Valid values for the Okta locale attribute require a concatenation of the ISO 639-1 two-letter language code, an underscore, and the ISO 3166-1 two-letter country code (for example, en_US).
Solution
How to resolve the null value when mapping the location attribute?
Choose one of the following methods to resolve the null value issue when mapping the location attribute:
- Convert the location attribute to match the required format of the Okta locale property.
- Create a custom attribute in the Okta profile to store the location data exactly as it appears in the profile source.
