How to dynamically map the OBO(On Behalf Off) tag with the users who has logged in for OSTS authentication without using the hard coded credential user store?
(Doc ID 1449626.1)
Last updated on OCTOBER 18, 2019
Applies to:Oracle Web Services Manager - Version 184.108.40.206.0 to 220.127.116.11.0 [Release 11gR1]
Information in this document applies to any platform.
Consider having different clients calling web services. OWSM policies are being used to protect those web services.
Client Side policy: "oracle/wss11_sts_issued_saml_with_message_protection_client_policy"
Server side policy: "oracle/wss11_saml_token_with_message_protection_service_policy"
The web service client (WSC) gives a call to OSTS to authenticate the incoming user details and get an asserted SAML token response from OSTS.
While sending the request to OSTS, they have used the On-Behalf-Of tag in the request and send the actual user for authentication. The OBO (On-Behalf-Of) tag is taking the user details from the Credential Store (OWSM Credential store) where they have hard-coded the user.
The web service client then calls the service of the Web Service Provider (WSP) on behalf of the user with the SAML token in the header of the request.
Now, suppose we need to use the OBO tag in the assertion and send the actual user in the OBO tag for authentication. The user details in the OBO tag are taken from a hard coded credential store, not the actual user who has logged in.
In this case, how do we dynamically map the OBO tag with the user who has logged in with OSTS authentication without using the hard coded credential user store?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document