Custom Attributes Created in Active Directory are Displayed in the Incorrect Language in Okta
Last Updated:
Administration
Okta Classic Engine
Directories
Okta Identity Engine
Overview
When creating, importing, and mapping custom Active Directory (AD) attributes, the attributes display in the incorrect language in Okta. For example, Unicode-based attributes appear as Base64 after being mapped. This occurs because AD agents read new custom attributes as Base64 until they are restarted. Restart every Okta AD agent connected to the domain and perform a full import to resolve the issue.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- Active Directory
- Custom Active Directory Attributes
- Attribute Mapping
Cause
AD agents read new custom attributes as Base64 until they are restarted.
Solution
How does Okta display custom Active Directory attributes in the correct language?
Restart every Okta AD agent connected to the domain and perform a full import to display the custom attributes in the correct language.
- Restart every Okta AD agent connected to the domain.
- Perform a full import.
