You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2004/01/29 16:15:18 UTC
DO NOT REPLY [Bug 26236] -
JAASRealm and GenericPrincipal
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26236>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26236
JAASRealm and GenericPrincipal
carlows@unerj.br changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |INVALID
------- Additional Comments From carlows@unerj.br 2004-01-29 15:15 -------
Well... I've tried to reproduce the bug... I've created my own LoginModule,
and two classes wich implements de java.security.Principal interface (one for
the user principal and other to the roles principals) just like the bug
description said, and it worked fine!
I also couldn't figure out how the method hasRole() in the RealmBase class can
be related to this problem because the method createPrincipal() (which is
called by the authenticate() method in the JAASRealm class) creates a
GenericPrincipal, as expected by the hasRole() method.
I think the problem can be related to the LoginModule of your application,
maybe it's not returning any RolePrincipal or something like that.
I'll change the bug status to INVALID, if you got any new information, you can
reopen it.
---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-dev-help@jakarta.apache.org