
sdipm (sdipm) asked a question.
I have one custom User Type Agent and I added custom attribute called GUID. I used OKTA update API to update the GUID value. like below.
{"profile": {"GUID": "abide"}}
I need to use the GUID attribute of Agent user type in SAML application means in SAML assertion I need to pass the GUID attribute. Each user will own have different GUID, none of the user will have same GUID.
So my question is how can I pass the GUID attribute in SAML application as attribute in terms of variable.
I am passing like below. but in SAML assertion , I see GUID as. Agent.GUID only, its. not picking up the value I have set above in update profile API.
Name. Name Format. Value
GUID. Unspecified. Agent.GUID

@sdipm (sdipm) please reference:
https://support.okta.com/help/s/question/0D74z00000CLspSCAT/detail
Thanks for the reply. I have follow up question based on your answer.
I have added the custom attribute GUID to 3 places - Default Profile(User), Custom User Type(Agent) and apps type user(got created after Application creation)
So my question is "how many places i need to add the custom attribute"?
If i don't add the custom attribute to Default Profle(user), how can i use your approach to map the attribute?
Hello @sdipm (sdipm) Thank you for reacting out to our Community!
Please see this article that provides a guide on how to achieve this:
https://support.okta.com/help/s/article/How-to-define-and-configure-a-custom-SAML-attribute-statement?language=en_US
Community members help others by clicking Like or Select as Best on responses. Try it today.
Hi Paul,
Thanks for the reply. I have follow up question based on your answer.
I have added the custom attribute GUID to 3 places - Default Profile(User), Custom User Type(Agent) and apps type user(got created after Application creation)
So my question is "how many places i need to add the custom attribute"?
If i don't add the custom attribute to Default Profle(user), how can i use your approach to map the attribute?
Best practices recommend to have the attribute in the Okta User profile. My recommendation is to add the attribute in the user profile to make sure the information is passed along properly.
Thanks, the thread can be closed now