topic Re: ldap configuring problem in Alfresco Archive

ldap configuring problem

paulrda — Wed, 22 Jun 2016 05:10:29 GMT

i referred activiti admin guide to configure ldap.( https://docs.alfresco.com/activiti/docs/admin-guide/1.4.0/#externalIdentityManagement )after configuring i got this error. i do have valid license to activiti and i get this license problem only when i try to use ldap. 22-Jun-2016 10:33:05.411 INFO

Re: ldap configuring problem

paulrda — Wed, 22 Jun 2016 05:20:05 GMT

im using apache directory studio to configure ldap.

Re: ldap configuring problem

jbarrez — Wed, 22 Jun 2016 08:30:44 GMT

Is this error coming from the admin app? If so, you need to properly configure the 'endpoint' in the admin app. It uses a REST call to determine the installed nodes.

Re: ldap configuring problem

paulrda — Wed, 22 Jun 2016 09:41:48 GMT

this error comes when i start the activiti bpm suite using ./start-activiti.sh command. i can access activiti-admin but cant access activiti-app page.

Re: ldap configuring problem

paulrda — Wed, 22 Jun 2016 09:43:55 GMT

Re: ldap configuring problem

hari — Thu, 23 Jun 2016 05:15:06 GMT

Hi,

This is just a hint and might not be the exact solution you are looking for. Please check if you have any duplicate(different versions) commons-lang3 jar's in your activiti-app's lib folder. We ran into the very same issue after placing one into that folder and it took us a lot of time to realize that.

Re: ldap configuring problem

vsangal — Tue, 13 Jun 2017 23:57:27 GMT

I have a same problem.. Can't find a solution.. here are my settings in activiti-ldap.properties. Am I missing some other configuration ?

ldap.authentication.enabled=true
ldap.authentication.casesensitive=false
ldap.authentication.java.naming.provider.url=ldap://<masked>:<masked>
ldap.authentication.dnPattern=uid={0},ou=<masked>,dc=<masked>,dc=com

Re: ldap configuring problem

vsangal — Thu, 15 Jun 2017 17:42:41 GMT

I was able to pass through this. After enabling LDAP i was still using default admin username to connect. But since that user does not exist in LDAP, end point was failing. I had to alter another configuration to chain the authentication to use either LDAP or local users.