User16611993307764082978 (Customer) asked a question.
SAML assertion for Custom SAML 2.0 app not populating.
I am attempting to setup SAML 2.0 into an application that requires custom attributes in the SAML assertion. I have set these attributes and mapped them in the default Okta user profile in the Profile Editor. I then added those same values in the customer attribute settings for the SAML app, but they are not populating in the assertion.
Example: Created custom value "cip_sid" under Okta Profile User in Profile Editor. This is mapped to the on-prem AD "objectSID" value.
When I add the custom attribute in the SAML setup for the app, I set the value as "user.cip_sid". When viewing the SAML assertion, the value is blank.
Is there additional steps I am missing?
Hi @User16611993307764082978 (Customer) , Thank you for reaching out to the Okta Community!
Tested the functionality to confirm and it’s working as expected.
When you say “viewing the SAML assertion”, are you leveraging something like SAML tracer to capture an end-user authentication or are you testing the inbuilt “Preview the SAML assertion” tool available when configuring the app? That one will show how the assertion will look like for your particular user account and might not be relevant to the other users.
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!
--------------------------------
Ask the Experts: Okta Device Access Product Team Now Thru 3/22