<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D54z00009oLQrSCAWOkta Classic EngineDirectoriesAnswered2023-11-02T17:48:18.000Z2023-11-01T16:06:50.000Z2023-11-02T17:48:18.000Z

LandonP.92160 (Customer) asked a question.

User import skipped attribute givenname is null

When I go to import users using the ldap agent/ldap integration I have some users that are skipped on the import with the below warning message:

 

Expected required AD attribute: givenname, (Okta attribute: firstName) to not be null. Please consult with your Active Directory admin if you believe this user should be imported.

 

I have set firstName to be optional in Profile Editor for the "to okta" provisioning settings but it is still a required field. I have also tried to use a ternary operator to convert nulls into actual values. What else can I do that might make givenname/firstName optional?


This question is closed.
Loading
User import skipped attribute givenname is null