Okta Fails to Find BambooHR Custom Attributes During Schema Discovery
Last Updated:
Overview
Okta fails to find BambooHR custom table attributes during schema discovery because Okta only imports attributes from the BambooHR user object schema. Resolve this issue by adding the custom attribute to the BambooHR user object before refreshing the schema attribute list in Okta.
Applies To
- Okta Identity Engine (OIE)
- Okta Classic Engine
- BambooHR
- Provisioning
- Schema Discovery
Cause
Okta only imports attributes from the BambooHR user object schema. Okta cannot import attributes from a BambooHR custom table.
Solution
How are BambooHR custom attributes imported into Okta?
Add the custom attribute to the BambooHR user object and refresh the schema attribute list in Okta to resolve the issue.
- Add the custom BambooHR attribute to the BambooHR user object. Contact BambooHR Support for assistance with creating a custom attribute in the BambooHR user object schema.
- Refresh the schema attribute list in Okta.
- Verify that the new custom BambooHR attribute is displayed and available for selection.
