BPM 184.108.40.206 Unable To Propagate The Identity Of The Authenticated User From SCA To OSB Using OWSM SAML Policy
(Doc ID 1631699.1)
Last updated on OCTOBER 25, 2016
Applies to:Oracle Business Process Management Suite - Version 220.127.116.11.0 to 18.104.22.168.0 [Release 11gR1]
Information in this document applies to any platform.
Customer has a BPM-Process which makes a Service-Call to OSB (Oracle-Service-Bus) Proxy-service. This proxy-service uses OWSM (Oracle-WebService-Manager)-SAML-Policies. On the OSB-side Customer needs to get the Subject but it is anonymous in the case that BPM-InitiatorTask in invoked via a Java-Client. The same works in 22.214.171.124.x, but in 126.96.36.199.7 with WLS 10.6.6 it does not work Further details: It works if Task has been invked from BPM-Workspace by clicking on Application Link It works if Process gets invoked with SOA-Direct-BindingClient
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