[Security & JAAS/JBoss] - Getting started with LDAP
by mata98
Hi all,
I'm an newby in AS development, so excuse my ignorance (and my joggled english).
Actually I'm challenged with the implementation of the security layer of my application (called tms).
My configuration:
I put the client-application as jar-file with all further needed libraries into one war-file, next with the server ejb and further service archives into one (huge) ear-file. Deployment without any security works fine.
I have to meet the requirement to verify the login against LDAP,
so I set up my application policy in server/tms/conf/login.config.xml:
| <application-policy name = "tms">
| <authentication>
| <login-module code="org.jboss.security.auth.spi.LdapLoginModule"
| flag="required">
| <module-option name="java.naming.factory.initial">
| com.sun.jndi.ldap.LdapCtxFactory
| </module-option>
| <module-option name="java.naming.provider.url">
| ldap://ldapserver:389/
| </module-option>
| <module-option name="java.naming.security.authentication">
| simple
| </module-option>
|
| <module-option name="password-stacking">useFirstPass</module-option>
|
| ....
|
| </login-module>
| <login-module code="org.jboss.security.ClientLoginModule"
| flag="required">
| <module-option name="password-stacking">useFirstPass</module-option>
| </login-module>
| </authentication>
| </application-policy>
|
I configured my web-application in war/web-inf/web.xml:
| <security-constraint>
| <web-resource-collection>
| <web-resource-name>restricted</web-resource-name>
| <url-pattern>/*</url-pattern>
| </web-resource-collection>
| <auth-constraint>
| <role-name>tms.user</role-name>
| </auth-constraint>
| <transport-guarantee>NONE</transport-guarantee>
| </security-constraint>
|
| <login-config>
| <auth-method>BASIC</auth-method>
| <realm-name>TMS</realm-name>
| </login-config>
|
| <security-role>
| <role-name>tms.user</role-name>
| </security-role>
|
As result, when requesting my application from within a webbrowser (localhost:8080/tms) I see a standard web-login dialog, the login works fine, it even refuses wrong user/passwords ;).
But the first try to request an EJB fails with
anonymous wrote : [LdapLoginModule] Bad password for username=null
So what's missing, how do I propagate the principal/credential from the initial login to the EJB-request ?
One further challenge: I have to modify the Login dialog to insert a further 'mandatory' field, where can I configure and introduce my own dialog ?
Thanks in advance,
Matz
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056823#4056823
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056823
18Â years, 10Â months
[Installation, Configuration & Deployment] - Using xalan.jar 2.5.0 for deployed applications
by jaysperk
I am trying to use xalan.jar version 2.5.0 in our deployed applications because we need that particular version to integrate with a third party library. Unfortunately, this version of xalan.jar includes bcel code that is incompatible with the version jboss uses. It seems that the bcel code is being load from the xalan.jar in .../server/myserver/lib/endorsed instead of the bcel.jar that resides in .../server/myserver/lib. The bcel.jar in .../server/myserver/lib contains the code required by jboss. Is there any way around this? Here is the error I receive:
java.lang.NoSuchMethodError: org.apache.bcel.generic.InstructionFactory.createNewArray(Lorg/apache/bcel/generic/Type;S)Lorg/apache/bcel/generic/Instruction;
at org.jboss.proxy.compiler.ProxyImplementationFactory.createProxyMethod(ProxyImplementationFactory.java:333)
at org.jboss.proxy.compiler.ProxyCompiler.getCode(ProxyCompiler.java:181)
at org.jboss.proxy.compiler.Runtime.makeProxyType(Runtime.java:83)
at org.jboss.proxy.compiler.ProxyCompiler.(ProxyCompiler.java:90)
at org.jboss.proxy.compiler.Proxies$Impl.newTarget(Proxies.java:618)
at org.jboss.proxy.compiler.Proxies.newTarget(Proxies.java:92)
at org.jboss.proxy.compiler.Proxy.newProxyInstance(Proxy.java:63)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCCreateBeanClassInstanceCommand.(JDBCCreateBeanClassInstanceCommand.java:70)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCCommandFactory.createCreateBeanClassInstanceCommand(JDBCCommandFactory.java:139)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.startStoreManager(JDBCStoreManager.java:478)
at org.jboss.ejb.plugins.cmp.jdbc.JDBCStoreManager.start(JDBCStoreManager.java:396)
at org.jboss.ejb.plugins.CMPPersistenceManager.start(CMPPersistenceManager.java:172)
at org.jboss.ejb.EntityContainer.startPmAndInterceptors(EntityContainer.java:1063)
at org.jboss.ejb.EjbModule.startService(EjbModule.java:422)
at org.jboss.system.ServiceMBeanSupport.jbossInternalStart(ServiceMBeanSupport.java:289)
I tried to add the following entry in jboss-service.xml but that did not seem to help:
I also tried this:
I know the offending bcel code is coming from xalan.jar but I don't know how to get it to load from bcel.jar instead. Any help is greatly appreciated.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4056817#4056817
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4056817
18Â years, 10Â months