<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
0D54z0000AHWtH6CQLOkta Classic EngineSingle Sign-OnAnswered2025-03-31T09:03:23.000Z2024-10-31T19:08:07.000Z2024-11-01T16:12:45.000Z

qlm39 (qlm39) asked a question.

Changing the external namespace of a custom application profile attribute

We've got a legacy SAML application, which has a few custom attributes. Now we want to add SCIM support, but the attributes are not included on the SCIM payloads. If we add a new attribute and set the external namespace, the attribute is included just fine. What can we do to have the attributes included in the payload? Can we set the external namespace on existing attributes?


  • Hi @qlm39 (qlm39)​ , Thank you for reaching out to the Okta Community! 

     

    I've taken a look at a random custom SAML app on my end and I'm not seeing the option to edit the external namespace of an attribute. 

    There is this article that references it, but it's explicitly for the Zoom app. 

    If this is a custom app, I recommend reaching out to my Developer colleagues via devforum.okta.com , as custom SCIM is their purview.  

    If you are the app owner/vendor and are trying to publish a new version of the app with SCIM provisioning to the Okta Integration Network catalog, you need to get in touch with the OIN Team via oin@okta.com as per this article.  

     

     

     

    If my answer helped, remember to mark it as best to increase its visibility for other members of the Okta Community who might have the same questions as you. 

     

    Hope my answer helps! 

     

    --

    Help others in the community by liking or hitting Select as Best if this response helped you.

    Expand Post

Loading
Changing the external namespace of a custom application profile attribute