I’m working on integrating SCIM provisioning between my application and Okta. My application includes some custom user attributes that are not part of the Core SCIM user attributes.
I want to know if there is a way to configure Okta to automatically detect these custom user attributes from my application and map them to the appropriate fields in the Okta user profile for provisioning purposes.
Here are a few specific questions I have:
Custom Attribute Detection: How can I set up Okta to automatically detect custom user attributes from my application’s SCIM endpoint?
Automatic Mapping: Referring to the guide doc, I’m currently adding my custom attributes manually with my custom external namespace. Is there a way to configure Okta to automatically map these custom attributes to the corresponding fields in the Okta user profile?
Any guidance, documentation, or examples would be greatly appreciated.
Custom Attribute Detection: Okta cannot automatially detect custom user attributes from your applicatoin’s SCIM endpoint.
Okta requires manual configuration to recognize and use these attributes.
Automatic Mapping: Okta doesn’t support fully automatic mapping for custom attributes, we need to still manually configure the attribute mapping in Admin console ( Under Provisioning > AttributeMapping section)
Hi,
I think you could automate some things, but I’m not quite sure the thing would be worth the pain.
With APIs, you could compare schemas for the app profile, the Okta user profile, list all inexisting attributes regarding what your source has. Then, you could update the schemas, and use the Mappings API to do the needed mappings.
Yet, it involves developing with loops, conditions, and moreover you would have to handle several complex JSON objects for the schemas and mappings.
In fact, I’m not actually 100% sure it can be done, this is just something I thought of.
Unless you have time and resources, it will probably be easier to do it manually in the Okta admin console like @SitaRam said.