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 2008/05/02 00:57:12 UTC

DO NOT REPLY [Bug 43214] Calls to Embedded.setRealm(Realm) fails

https://issues.apache.org/bugzilla/show_bug.cgi?id=43214


Mark Thomas <ma...@apache.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |INVALID




--- Comment #1 from Mark Thomas <ma...@apache.org>  2008-05-01 15:57:12 PST ---
This looks to be as designed to me. You have updated the default Realm after
you create the engine. You need to do things the other way around.

embeddedCatalina.setRealm() sets the default realm for new components. You
don't need to set the appName - it should be set as a result of the call to
engine.setRealm() in Embedded.createEngine()

You could also create your Realm and add it directly to the new Engine.

As far as I can tell from reading the code, adding a JAASRealm to any container
will result in the JAASRealm taking on the name of the container as returned by
Container.getName()


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org