nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Contextless LDAP authentication

eron123

Hi team,

We have Alfresco 1.2.1 running and authenticating using simple bind to an LDAP directory (eDirectory, which conforms to OpenLDAP). We would like to configure Alfresco to login without context. As the users are in different containers, we can not use a string like the following:

'cn=%s,o=alfresco'

We have also tried configuring MD5 Digest, but this did not solve the problem either.

How can Alfresco be configured for contextless login?

Thanks.

Find more posts tagged with

Comments

andy

Hi

I am not sure exactly what the issue is here….

You could use chainging authentication. This allows an ordered list of authentication services to be specified. You could have multiple LDAP repos or multiple branch locations for users in the same LDAP repo. You can use abstract spring beans for the common configuration.

Digest MD5 should solve the problem. What was the issue here?

Regards

Andy

eron123

Andy,

We want to have a user log in with just thier uid (in eDirectory, this is the CN attribute). This means the alfresco login module should search the tree for the user with that name to authenticate to. Since users are in various containers in the tree, we can not hard-code a container like in the example.

The users don't know their full DN, and forcing them to enter it is not desirable anyway.

What are the options for solving this? Should the MD5 Digest solution take care of this?

andy

Hi

It sounds like the best thing is to configure chaining authentication to use an LDAP authentication service against the same repo for each path where you have users. They can then use the cn to login.

MD5 authentication would still have to be able to find users - but it would involve a search based on uid attribue to find the user and therefore get the password. The search would not need to be restricted by path and is done on the ldap server. Your users would have to type in the uid. The wiki contains information on how to set up md5 authentication for open ldap.

Regards

Andy