SecurityContext EL expression not working

Question

When trying to apply this:
#{securityContext.userInRole['roleList']}
... (#{securityContext.userInRole['Administrator']})
... (#{securityContext.userInRole['Administrator,Spaces-User']})
to portlet visibility flag in Spaces it always returns false.
Bug or Feature ?
petri.
Edited by: psavolai on 14.4.2010 6:54

Answer 1

Did oracle respond with a solution to passing roles from WebCenter portal to a ADF portlet?
We have the following code inside of both the portal and the portlet:
Username: #{facesContext.externalContext.remoteUser}
is vendor: #{securityContext.userInRole['vendor']}
is buyer #{securityContext.userInRole['buyer']}
In the portal we get back the correct username along with "true" for both userInRole calls. This is correct. However in the portlet it does return the correct username, however both roles return "false". The roles defined in web.xml & portlet.xml on the ADF porlet side both have the vendor/buyer definitions:
portlet.xml:
<security-role-ref>
<role-name>vendor</role-name>
</security-role-ref>
<security-role-ref>
<role-name>buyer</role-name>
</security-role-ref>
web.xml:
<login-config>
<auth-method>CLIENT-CERT</auth-method>
</login-config>
<security-role>
<description>vendor role</description>
<role-name>vendor</role-name>
</security-role>
<security-role>
<description>buyer role</description>
<role-name>buyer</role-name>
</security-role>
Within the portal, we define the portlet producer which prompts for the user categories. I've mapped them to the J2EE roles via the dropdown lists. They have the same name on both sides buyer=buyer, vendor=vendor.
I've sniffed the raw HTTP traffic from the portal to the portlet and I can see this (snippit of the larger XML):
<ns0:userContext>
<ns0:userContextKey>weblogic</ns0:userContextKey>
<ns0:userCategories>buyer</ns0:userCategories>
<ns0:userCategories>vendor</ns0:userCategories>
<ns0:profile/>
</ns0:userContext>
As you can see it sends he user name (weblogic is the username) and the two roles I'm in. However this does not seem to get mapped in the ADF portlet side. So it would seem that the configuration on the portal is correct, but something is wrong / misconfigured on the portlet side as these categories are not getting mapped into into the ADF security context.
By the way I'm using 11gPS2