Thanks for the response, sorry for the delay in digesting this... It seems like the AuthenticationManager and RealmManager interfaces don't have any particularly sensitive methods related to them, so my guess is the only reason that these aren't already available remotely is because they are different per web application? Correct me if I am wrong, but this solution seems like it would only support one login context per JNDI tree.
If that's the case, one option would be to parameterize the instantiation of JBossSecurityMgrRealm with the name of a java:comp/env/security subcontext to use. This would solve this issue, but are working patches of this nature something that you would consider applying or is this a misguided hack? happy ny! -b > -----Original Message----- > From: Scott M Stark [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 18, 2002 9:24 PM > To: [EMAIL PROTECTED] > Subject: Re: [JBoss-user] Standalone Tomcat 4.1 and JAAS > > > The ClientLoginModule is just a wrapper around the > SecurityAssociation thread > local variable accessors and the JBossSecurityMgrRealm uses > this directly. It > also uses the AuthenticationManager and RealmMapping of the security > manager associated with the web app. This is obtained through > JNDI, and this > is not available remotely from the JBoss server. This is what > you need to work on. > > You could use the JBossSecurityMgrRealm as is if you created a JNDI > ObjectFactory binding under java:comp/env/security that > supported lookups > of the "securityMgr" and "realmMapping" bindings, and returned remoted > proxies for the corresponding AuthenticationManager and RealmMapping > interfaces of the security manager. Its doable since all the > interface objects are > compatible with RMI, its just going to take some work. > > xxxxxxxxxxxxxxxxxxxxxxxx > Scott Stark > Chief Technology Officer > JBoss Group, LLC > xxxxxxxxxxxxxxxxxxxxxxxx > > ----- Original Message ----- > From: "Brian Topping" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Wednesday, December 18, 2002 4:59 PM > Subject: RE: [JBoss-user] Standalone Tomcat 4.1 and JAAS > > > > -----Original Message----- > > From: Scott M Stark [mailto:[EMAIL PROTECTED]] > > Subject: Re: [JBoss-user] Standalone Tomcat 4.1 and JAAS > > > > > > Its not going to work. The JBossSecurityMgrRealm is > designed for being > > embedded in JBoss. You would have to modify it significantly to run > > standalone. > > Hi Scott, > > Fair enough, thanks for the clue... > > So I'm wondering if you would consider my wanting to make > said significant > modifications to be possible with existing APIs on the server > side. I'm > guessing the result would be something that needs to be a > selection of meaty > bits from both the JBossSecurityMgrRealm and ClientLoginModules. > > Am I on the right track here? Are there any potential API > issues that you > know of that would cause this to be impossible from a design > standpoint? > > Thanks for your consideration, > > -b > > > > ------------------------------------------------------- > This SF.NET email is sponsored by: Order your Holiday Geek > Presents Now! > Green Lasers, Hip Geek T-Shirts, Remote Control Tanks, > Caffeinated Soap, > MP3 Players, XBox Games, Flying Saucers, WebCams, Smart Putty. > T H I N K G E E K . C O M http://www.thinkgeek.com/sf/ > _______________________________________________ > JBoss-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/jboss-user > ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
