Activiti LDAP Integartion - Activiti Explorer Doesn't Work

[bsethuramalinga]

Hi,

I am trying to get configured with our enterprise LDAP which is Novell E-Directory.  I have followed all the steps suggested by the book, Activiti in Action. Implemented UserManager, GroupManger from the sample code provided in "Activiti In Action" book.

From the debug messages, I am able to see my user-id  is validated with LDAP and the result is positive but still fails to render the Activiti-Explorer. It just hangs at Activiti-Explorer login page. No further error messages. Nothing.

But if I remove LDAP configuration,  everything looks good with KERMIT id and  I am able to see Activiti-Explorer like 'fresh out-of-the-box'

My Setup
Tomcat 7.0.34
Activiti 5.12 or 5.12.1
Browser : IE or Firefox. (Cleared the cache each time before I login).

I had it working with Activiti 5.11 , which I was able to configure for 5.11 but lost the code. ..?
In 5.12, I see the ClassNames for User and Group objects changed to
org.activiti.engine.impl.persistence.entity.User –to–> org.activiti.engine.impl.persistence.entity.UserEntity
org.activiti.engine.impl.persistence.entity.UserManager –to–> org.activiti.engine.impl.persistence.entity.UserEntityManager

Do these changes make a difference..?


Where is the problem….? What is the necessary LDAP(Apache Standard) related JAR files I should have in Tomcat Server Classpath/Activiti-Explorer's WEB-INF/lib folder..?
If possible, please provide complete list of integrating Activiti with enterprise LDAP servers.

Please advise on  how to troubleshoot the problem.   

Any help is appreciated.

[frederikherema1]

I'm not sure what JAR's you actually need for working with the LDAP. You don't see any exception stracktraces either?

Can you perhaps debug the code you wrote (for fetching the user) to sea if it, at least, gets there? If not, try debugging org.activiti.explorer.ui.login.DefaultLoginHandler.authenticate(…)

[desperado]

Hi,

just a short feedback.

minor traps maybe…

* ensure the UserId fulfills case sensitive
* ensure, if you are connected to an own db, that the ldap user is synchronized with the db
  - if so, to avoid further problems switch of auto generation of the data if the inMem DB is written once to the DB

browser issues maybe…

* maybe you have a specific problem with browser configuration ( beside some caching issues ) check addons and
  security settings. You may try another browser version ( and in worst case a full cleanup of the prior version you currently use)

* i used a third browser because of different behaviour in some situations

implementation problems

* to get a stand alone ldap solution ( without using third libraries ) you may have a look here.
  Therefore you will need some more information about JNDI.

http://forums.activiti.org/content/processengineconfiguration-ldapadapter

* you noticed changes already correctly ( at least what i was able to read )

you can check the logs of Activiti and and tomcat to get more information,
what is going wrong, therefore it maybe easier to help.

so, just some ideas…

Regards,

Michael