<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
Custom Attributes for an Org2Org App Profile are Not Displayed after Clicking "Refresh Attribute List" in the Profile Editor
Okta Integration Network
Okta Classic Engine
Okta Identity Engine
Overview

It may be noticed that there are no custom attribute values being fetched after following the steps from the How to Integrate a Custom Attribute in an Org2Org Integration article.


None of the custom attributes defined in the Hub org's Okta User (Default) are returned after clicking on the Refresh Attribute List button, and there is no visible error exception during app schema import.
 

Applies To
  • Org2Org app user schema import
  • Okta Integration Network
  • Empty Custom Attribute List returned during "Refresh Attribute List" in Profile Editor
Cause

The Org2Org app schema import will be from the API token owner's Okta user profile schema. Okta allows the creation of custom Okta User types while maintaining a separate set of custom attribute definitions. 

 

Below are potential causes: 

  1. The custom user attributes are set under the Okta User (Default) profile schema, which was intended to be imported during schema import. The API token owner has a custom Okta user type set.
  2. The custom user attributes are set under the custom Okta User type profile schema, which was intended to be imported during schema import. The API token owner has the User (Default) Okta user type.
Solution
  1. In the Hub org where the API token was generated for Org2Org provisioning, please double-check the API token Owner's User Profile and confirm their Okta User Type.
  2. Verify which Okta User Type Profile Schema the set of custom attributes is imported from.
  3. Ensure the custom attributes desired for import in the Org2Org provisioning mapping are in the correct Okta User Profile Schema. 
  4. Regenerate a new API token with an Okta Admin of the desired Okta user schema import (or has the custom attribute defined).
  5. Copy the new API token generated by the correct Okta Admin user account and replace the existing API token in Spoke Org > Okta Admin > Applications >  Org2Org app > Provisioning > Integration > Edit.
    • Click Test API Credential, and click Save after successful verification.
  6. Navigate to the spoke org > Okta Admin > Applications >  Org2Org app > Provisioning > To App > Profile Editor, and then click on Add Attribute > Refresh Attribute List. The custom attributes should be imported correctly this time.

Pick Schema Attributes  

 

Related References

Loading
Custom Attributes for an Org2Org App Profile are Not Displayed after Clicking "Refresh Attribute List" in the Profile Editor