JBoss JAAS Security Domain
curtisb Aug 12, 2005 3:24 PMOk, guys and gals, sorry for all the questions.
I have managed to finally get by one of my errors and now I am having another error. I am using DynamicLoginConfig successfully however, if I put my security domain as the following I get a failed to create security manager stacktrace.
<security-domain>java:jaas/overdrive</security-domain>
Now, if I make it just the following, it seems to create the security manager successfully but then I get a Tomcat dump.
javax.naming.NameNotFoundException: overdrive not bound
Does anybody have any ideas what the problem might be?
JBoss Service.xml
<server> <!-- ==================================================================== --> <!-- Security --> <!-- ==================================================================== --> <mbean code="org.jboss.security.auth.login.DynamicLoginConfig" name="jboss:service=DynamicLoginConfig"> <attribute name="AuthConfig">META-INF/login-config.xml</attribute> <depends optional-attribute-name="LoginConfigService"> jboss.security:service=XMLLoginConfig </depends> <depends optional-attribute-name="SecurityManagerService"> jboss.security:service=JaasSecurityManager </depends> </mbean> </server>
LoginConfig.xml
<?xml version='1.0'?> <!DOCTYPE policy PUBLIC "-//JBoss//DTD JBOSS Security Config 3.0//EN" "http://www.jboss.org/j2ee/dtd/security_config.dtd"> <policy> <application-policy name="overdrive"> <authentication> <login-module code="com.kadt.security.LoginModule" flag="required"> <module-option name="url">jdbc:sapdb://localhost/dms?sqlmode=ORACLE</module-option> <module-option name="driverClass">com.sap.dbtech.jdbc.DriverSapDB</module-option> <module-option name="debug">true</module-option> <module-option name="ignorePasswordCase">false</module-option> </login-module> <login-module code="org.jboss.security.ClientLoginModule" flag="required"></login-module> </authentication> </application-policy> </policy>
JBossWeb.xml
<jboss-web> <security-domain>overdrive</security-domain> <class-loading java2ClassLoadingCompliance="false"> <loader-repository> sf:loader=sf.war <loader-repository-config>java2ParentDelegation=false</loader-repository-config> </loader-repository> </class-loading> <module> <service>authService.sar</service> </module> </jboss-web>