Forgot to forward this to the list.
On Fri, Jan 28, 2011 at 9:40 AM, Laird Nelson <ljnelson_at_gmail.com> wrote:
> On Fri, Jan 28, 2011 at 3:55 AM, Nithya Subramanian <
> Nithya.Subramanian_at_sun.com> wrote:
>
>> You can re-use the GlassfishRoleMapper class that is present in the same
>> package for using the existing GF principal-role-mapping.
>>
>
> OK; thanks.
>
>
>> If you follow the code in SimplePolicyConfiguration, you can observe that
>> GlassfishRoleMapper is the default RoleMapper class that is loaded. To
>> override it, you can set a jvm-option:
>>
>>
>> <jvm-options>-Dsimple.jacc.provider.JACCRoleMapper.class=<custom-role-mapper-class></jvm-options>
>>
>
> OK, sure, if I'm using the SimplePolicyConfiguration, which I'm not. :-)
> I guess I can pursue a similar strategy. (I want to tread carefully here
> and not follow the source code because I don't want to get involved in
> licensing issues.)
>
> So there's no such thing, then, as a generic JACC provider that uses the
> application server vendor's role mapping subsystem? That is, I will have to
> have a Glassfish role mapper, a JBoss role mapper, a Websphere role mapper,
> and so on? That certainly *seems* to be the case.
>
> Best,
> Laird
>