Thanks Scott

I'm not sure I completely understand how all the parts in JBossSX interact yet (I'm RE-reading the chapter in the Admin-devel guide AGAIN, only slower and annunciating every syllable this time :-), but in the mean time I'll begin writing the login module.

So should the JaasSecurityDomain domain= be the same name as as my login module(s) application-policy name= in this case? If not, how is the relationship between the JaasSecurityDomain and the LoginModule defined?

Thanks

-jason

On Friday, November 15, 2002, at 10:03 AM, Scott M Stark wrote:

A LoginModule is all you need. The KeyStore should be coming from the
org.jboss.security.SecurityDomain the login module configuration belongs
to. Right now this is not passed in so I'll add it to the AbstractServerLoginModule
layer. In the interim get the SecurityDomain interface from JNDI. If you have a
JaasSecurityDomain like the following:

<mbean code="org.jboss.security.plugins.JaasSecurityDomain"
name="Security:name=JaasSecurityDomain,domain=RMI+SSL">
<constructor>
<arg type="java.lang.String" value="RMI+SSL"/>
</constructor>
<attribute name="KeyStoreURL">chap8.keystore</attribute>
<attribute name="KeyStorePass">rmi+ssl</attribute>
</mbean>

The SecurityDomain interface is obtained as:
SecurityDomain sd = (SecurityDomain) new InitialContext().lookup("java:/jaas/RMI+SSL");

xxxxxxxxxxxxxxxxxxxxxxxx
Scott Stark
Chief Technology Officer
JBoss Group, LLC
xxxxxxxxxxxxxxxxxxxxxxxx



-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing your web site with SSL, click here to get a FREE TRIAL of a Thawte Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/jboss-development

Reply via email to