Hi Gustav,
Gustav Bostrom wrote:
GB> Thanks for the help!
GB> I still didn't succeed though.
GB> *I login using my client code and the jBoss ClientLoginModule. This
GB> works fine.
GB> *I modified the standardjboss.xml to include the entries you mentioned ,
GB> but specifying my application name
Have added the entries to *all* "container-configuration" elements?
There are about 6 such places in standardjboss.xml.
Also check that there are no "container-configuration" elements in
your jboss.xml.
I've got no other ideas. Should work. Works for me ;-)
Oleg
GB> I then call a test method on my EJB to see if my logged in Principal is
GB> propagated to jBoss:
GB> ..
GB> System.out.println("And the entity context Principal is:");
GB> System.out.println(entityContext.getCallerPrincipal());
GB> ...
GB> Unfortunately the entityContext.getCallerPrincipal() still returns null.
GB> My server auth.conf looks like this:
GB> eonwrx {
GB> // Provides the default realm mapping
GB> org.jboss.security.SimpleServerLoginModule required;
GB> };
GB> Is there something more I need to do? It doesn't seem like the Server
GB> login module gets called at all, because it should throw a
GB> LoginFailedException in my case since I'm passing a different userid
GB> than password.
GB> Gustav
GB> -----Original Message-----
GB> From: Oleg Nitz [mailto:[EMAIL PROTECTED]]
GB> Sent: den 6 december 2000 16:22
GB> To: jBoss
GB> Subject: Re[4]: [jBoss-User] Security
GB> Hi jBoss,
GB> Gustav Bostrom wrote:
GB>> Hi Oleg !
GB>> This information was great. Now I just wonder what to put in my
GB>> jboss.xml.
GB> You need to modify jboss.xml only if non-standard container
GB> configurations are defined there.
GB> Otherwise you just need to modify standardjboss.xml: put inside each
GB> contained configuration the following lines:
GB> <container-configuration>
GB> ...
GB> <authentication-module>java:/jaas/other</authentication-module>
GB> <role-mapping-manager>java:/jaas/other</role-mapping-manager>
GB> ...
GB> </container-configuration>
GB> Or put your app. name specified in auth.conf instead of "other".
GB>> I'm also curious pn how the Login Information is passed from the
GB> client
GB>> side to the server side. Is the SecurityAssociation still used?
GB> Yes, JAAS security stuff is just a layer over the original jBoss
GB> security stuff.
GB> Best regards,
GB> Oleg
GB> --
GB> --------------------------------------------------------------
GB> To subscribe: [EMAIL PROTECTED]
GB> To unsubscribe: [EMAIL PROTECTED]
GB> Problems?: [EMAIL PROTECTED]
Best regards,
Oleg
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
