|
From: <sco...@jb...> - 2006-07-06 17:11:24
|
"soh...@jb..." wrote : | Right but the issue with using it this way with association with the LoginModule is that the LoginModule may not fire in 100% of usecases, as indicated. | | Looks like we kind of need a way to specify the role-mapping independent of the LoginModule, so that the roles are populated without dependence on particular LoginModule Correct. We need a separate authorization aspect(s) that can be applied to the authentication result to build up the authorization context independent of the authentication phase. Its a legacy overloaded usage of jaas that the login modules provide the declarative roles. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3955946#3955946 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3955946 |