dcw36 (dcw36) asked a question.
Integration of OKTA with Oracle Apex - Social sign in (Mapping Attribute Issue.)
From Okta Side we are getting user details, like department, name, email, pod
department, name, email => String
But pod type is String Array like => ["Green","Red","Yellow"]
So I am mapping in social sign in authentication at oracle apex side.
Additional user attributes => department,name,email,pod
Map Additional User Attribute To => :APP_DEPARTMENT,:APP_NAME,:APP_EMAIL,:APP_POD
So I am getting department,name,email but pod are not getting. Is that because pod type is String Array at okta side?
Or I have to write different syntax or way for pod in Additional user attributes.
Can anyone know about these?
Hello @dcw36 (dcw36) Thank you for reacting out to our Community!
I have does a test on my environment and I was able to have the value received in the SAML assertion. Can you do a SAML trace and see if the information is being send in the first place?
If the information is being sent, then make sure that you have the attributes mapped accordingly from the IPD to the SP.
Community members help others by clicking Like or Select as Best on responses. Try it today.
Watch and Learn: New Okta how-to videos, plus what's new this month in the May newsletter.
@paul.stiniguta (Okta, Inc.)
Did you test with Oracle Apex - Social Sign in?
Are you getting String array from OKTA to Apex?
SAML trace we have to do at Oracle apex side or okta side?
Thanks,
Shitul