Oracle OES: Possible to use XPath wildcards in OES authorization policies?

Question

Hi,
I have policies to authorize WS-requests using OES through OWSM.
In the OES policies I retrieve attributes from the WS-request using XPath expressions.
When I use namespace in my XPath it all works well:
NAMESPACE tns=http://myns/
myAttr //tns:myVal
But I have several WS-requests that have different namespaces, but that i need to authorize using the same policy, so I would like to use a wildcard for the namespace. But when I try the attribute retriever doesn't find the node value:
myAttr //*:myVal
When i use tools to check the XPath, like SoapUI, I am able to get the node value using the expression above.
Does anyone have experience using XPath wildcards in OES policies?
-T

Answer 1

I understand that the LDAP structure design depends on the business goals and requirements and we are defnitely building the schema in that lines. But the thing we want to make sure is how flexible are the products like OIM, OAM and OES to provide user authentication(if the user is deep down in the tree), authorization (if the user needs to be authorized to services having attributes deep down in the tree), mapping complex relationships and permissions in conjunction with OID.
I think the other way of asking this question would be what we should take into consideration while designing the LDAP structure in OID as the backend LDAP store and what things we should leave whille designing LDAP structure in OID that could be considered while designing the authentication, authorization process in OIM, OAM and OES.
Our goal is to keep the LDAP structure simple and flexible but at the sametime use OAM, OES and OIM at their best capabilities to serve our purpose without lot of customizations required.
Thanks!