alfresco ldap Integration

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.

itsard

Hi all,
I need to configure LDAP with alfresco labs 3.0
My ldap-authentication.properties is like :

    #
    # This properties file brings together the common options for LDAP authentication rather than editing the bean definitions
    #

    # How to map the user id entered by the user to taht passed through to LDAP
    # - simple
    #    - this must be a DN and would be something like
    #      CN=%s,DC=company,DC=com
    # - digest
    #    - usually pass through what is entered
    #      %s     
    ldap.authentication.userNameFormat=cn=EMP_MST,dc=iwas,dc=in

    # The LDAP context factory to use
    ldap.authentication.java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory

    # The URL to connect to the LDAP server
    ldap.authentication.java.naming.provider.url=ldap://172.26.145.123:389

    # The authentication mechanism to use
    ldap.authentication.java.naming.security.authentication=SIMPLE

    # The default principal to use (only used for LDAP sync)
    ldap.authentication.java.naming.security.principal=cn=ldapadmin

    # The password for the default principal (only used for LDAP sync)
    ldap.authentication.java.naming.security.credentials=ldapadminpwd

    # Escape commas entered by the user at bind time
    # Useful when using simple authentication and the CN is part of the DN and contains commas
    ldap.authentication.escapeCommasInBind=false

    # Escape commas entered by the user when setting the authenticated user
    # Useful when using simple authentication and the CN is part of the DN and contains commas, and the escaped \, is
    # pulled in as part of an LDAP sync
    # If this option is set to true it will break the default home folder provider as space names can not contain \
    ldap.authentication.escapeCommasInUid=false‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍‍

I am not able to login into alfresco with either admin or any other user. At the server the error is :
org.alfresco.error.AlfrescoRuntimeException: Wrong authentication setup for alfresco authenticator.

I need neither a CFS nor a FTP configuration.
In the file-servers.properties there is an entry :
cifs.localname=${localname}
cifs.domain=
cifs.broadcast=255.255.255.255

Do I delete it as i dont need it.
I m trying to login with a user that is created in alfresco as well as configured in ldap server with the pwd that of ldap servers user.
Plz let me know where the prob is as I cant login into Alfresco????
Whats the use of CIFS server in alfresco

dward

The problem is that the default CIFS authenticator is not compatible with the LDAP authentication component.

A lot of progress has been made in this area in v3.2 and now your CIFS authentication settings are deterined automatically from your choice of authentication subsystem(s).

In v3.0 I'm afraid you're going to have to add this bean definition to custom-repository-context.xml.

   <bean id="fileServersConfigService" class="org.alfresco.config.xml.XMLConfigService" init-method="init">
      <constructor-arg>
         <ref bean="fileServersConfigSource" />
      </constructor-arg>
      <property name="properties">
         <list>
           <value>classpath:alfresco/file-servers.properties</value>
           <value>classpath:alfresco/extension/custom-file-servers.properties</value>
         </list>
      </property>
   </bean>
‍‍‍‍‍‍‍‍‍‍‍‍‍

and then add these settings to $TOMCAT_HOME/shared/classes/alfresco/extension/custom-file-servers.properties

cifs.enabled=false
ftp.enabled=false

In v3.2 cifs.enabled and ftp.enabled are directly controllable in alfresco-global.properties without all this messing around. Plus you wouldn't even need to change them because the CIFS server is automatically disabled if there is no compatible authenticator for it. Why not use labs 3.2?