OktaS.06027 (Customer) asked a question.
Initial Seup - AD Mapping Problem
When going through the initial setup it finds 2 fields that need mapping from our AD to Okta, or maybe vice versa. They’re the distinguishedName and the objectGUID fields. I’m not sure what to do about these. I assume that Okta will use and update our AD for authentication, and if domain passwords, for example, are changed, Okta will either communicate that with our AD or our AD will communicate that back with Okta so that they stay in sync. In any case, what am I supposed to use for mapping of these fields?
Okta during config will map only a small amount of attributes, if you select the default version.
If you require those attributes inside of Okta, you can map those to either existing attributes that are similar to what the two attributes contain, or create you own custom attributes to hold those values. It is not mandatory to have all attributes, but rather those that you require to be imported from Ad into Okta or sent from Okta to AD if you use that.