myOpenKM on LDAP auth

[ares]

I always get this error.

08:52:50,986 INFO [TomcatDeployer] deploy, ctxPath=/jmx-console, warUrl=.../deploy/jmx-console.war/
08:52:51,104 ERROR [URLDeploymentScanner] Incomplete Deployment listing:

--- MBeans waiting for other MBeans ---
ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
State: FAILED
Reason: java.lang.SecurityException: Invalid authentication attempt, principal=null
I Depend On:
jboss:service=TransactionManager
jboss.jca:service=DataSourceBinding,name=DefaultDS

ObjectName: jboss.mq:service=PersistenceManager
State: FAILED
Reason: org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (java.lang.SecurityException: Invalid authentication attempt, principal=null)
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
Depends On Me:
jboss.mq:service=DestinationManager

--- MBEANS THAT ARE THE ROOT CAUSE OF THE PROBLEM ---
ObjectName: jboss.mq:service=PersistenceManager
State: FAILED
Reason: org.jboss.mq.SpyJMSException: Could not resolve uncommited transactions. Message recovery may not be accurate; - nested throwable: (java.lang.SecurityException: Invalid authentication attempt, principal=null)
I Depend On:
jboss.jca:service=DataSourceBinding,name=DefaultDS
Depends On Me:
jboss.mq:service=DestinationManager

ObjectName: jboss:service=KeyGeneratorFactory,type=HiLo
State: FAILED
Reason: java.lang.SecurityException: Invalid authentication attempt, principal=null
I Depend On:
jboss:service=TransactionManager
jboss.jca:service=DataSourceBinding,name=DefaultDS


08:52:51,204 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-0.0.0.0-8080
08:52:51,263 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-0.0.0.0-8009
08:52:51,324 INFO [Server] JBoss (MX MicroKernel) [4.2.3.GA (build: SVNTag=JBoss_4_2_3_GA date=200807181439)] Started in 52s:307ms

Here's my login-config.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">

<application-policy name="OpenKM">
<authentication>
<login-module code="org.jboss.security.auth.spi.LdapExtLoginModule" flag="required" >
<module-option name="java.naming.provider.url">ldap://192.192.192.192:192</module-option>
<module-option name="bindDN">cn=Man\,Super Spider,ou=hero,ou=hiro,dc=heroes,dc=com,dc=ph</module-option>
<module-option name="java.naming.security.authentication">simple</module-option>
<module-option name="bindCredential">hahaha</module-option>
<module-option name="baseCtxDN">ou=hiro,dc=heroes,dc=com,dc=ph</module-option>
<module-option name="baseFilter">(sAMAccountName={0})</module-option>
<module-option name="rolesCtxDN">ou=hiro,dc=heroes,dc=com,dc=ph</module-option>
<module-option name="roleFilter">(sAMAccountName={0})</module-option>
<module-option name="roleAttributeID">memberOf</module-option>
<module-option name="roleAttributeIsDN">true</module-option>
<module-option name="roleRecursion">0</module-option>
<module-option name="roleNameAttributeID">cn</module-option>
<module-option name="searchScope">SUBTREE_SCOPE</module-option>
<module-option name="allowEmptyPasswords">false</module-option>
<module-option name="java.naming.referral">follow</module-option>
<!-- <module-option name="defaultRole">UserRole</module-option> -->
</login-module>
</authentication>
</application-policy>

[ares]

also it says that "No valid LoginModule configuriation for OpenKM"

[ares]

i got it.. i just reformatted an old Ubuntu laptop and started from scratch. this forum helped and gave me an idea. thanks!

[jllort]

solved ?

[ares]

yep.. solved..

[jllort]

We're happy for it. Good job, any ldap configuration is not trivial task.

[coldface]

Hi,
Could you pls share the reason and how to resolve it?
I met the same problem now
Appreciate