Policy Applied To Xpath Location/namespace Does Not Work If The Location Includes Two Namespaces
(Doc ID 2166861.1)
Last updated on OCTOBER 07, 2022
Applies to:
Oracle Web Services Manager - Version 11.1.1.7.0 and laterInformation in this document applies to any platform.
Goal
The OIM product provides a policy "oimcp_WS_CONNECTOR_OUTBOUND" to decrypt password fields before passing the content to endpoint web services.
This policy is used in the OIM WSConnector composites which can be customized based on specific endpoint web services.
In this case, the web service wsdl is referring to another wsdl and as a result, the path to their password variable (which is the field to decrypt) has two namespaces.
/ns3:addUser/ns3:user/ns4:password
The policy "oimcp_WS_CONNECTOR_OUTBOUND" requires two property values "password.field.xpath.locations" and "target.payload.namespaces" which can contain a list of comma separated namespace and locations.
However, no matter how these are declared, the policy is not applied because the xpath location is read to be null.
How can the system be set up in order to work the way that is desired?
Solution
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
Goal |
Solution |
References |