"beve" wrote : I can't really say that this was a technical reason for this.
It just seemed appropriate that the LoginModule should only do one thing and that was to
validate an existing token from a calling client.
Well login modules have two aspects to them, authentication is the first. The second
stage is to associate Principals/Credentials with the current security context.
The generation of the SAML context could be handled by this mechanism.
"beve" wrote : Sorry, I'm not following your suggested solution here. Could
you expand on what you mean for this to be handled indirectly with javax.security.
JAAS.
Kev
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4261260#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...