<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Alfresco authentication with zimbra ldap  in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-authentication-with-zimbra-ldap/m-p/292150#M245280</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi,&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Can't able to authenticate alfresco using zimbra mail server users,it gets "Failed to login,The remote server may be unavailable or your authentication details have not been recognized",here I posted my ldap-authentication.properties file which is in&amp;nbsp; "/opt/alfresco-4.2.a/tomcat/shared/classes/alfresco/extension/subsystems/Authentication/ldap/ldap1/ldap-authentication.properties",please help me to sort out&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Also I added authentication chain in alfresco-global.properties file:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; authentication.chain=alfrescoNtlm1:alfrescoNtlm,ldap1:ldap&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;My ldap-authentication.properties file:&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt; This flag enables use of this LDAP subsystem for authentication. It may be&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# that this subsytem should only be used for synchronization, in which case&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# this flag should be set to false.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.authentication.active=true&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# This properties file brings together the common options for LDAP authentication rather than editing the bean definitions&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.authentication.allowGuestLogin=false&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# How to map the user id entered by the user to that passed through to LDAP&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# - simple &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&amp;nbsp;&amp;nbsp;&amp;nbsp; - this must be a DN and would be something like&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; uid=%s,ou=People,dc=company,dc=com&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# - digest&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&amp;nbsp;&amp;nbsp;&amp;nbsp; - usually pass through what is entered&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; %s&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# If not set, an LDAP query involving ldap.synchronization.personQuery and ldap.synchronization.userIdAttributeName will &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# be performed to resolve the DN dynamically. This allows directories to be structured and doesn't require the user ID to&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# appear in the DN.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.authentication.userNameFormat=uid\=%s,ou\=people,dc\=xxxx,dc\=com&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The LDAP context factory to use&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.authentication.java.naming.factory.initial=com.sun.jndi.ldap.LdapCtxFactory&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The URL to connect to the LDAP server &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.authentication.java.naming.provider.url=ldap://IP-OF-Mailserver:389&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The authentication mechanism to use for password validation&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.authentication.java.naming.security.authentication=simple&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# Escape commas entered by the user at bind time&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Useful when using simple authentication and the CN is part of the DN and contains commas&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.authentication.escapeCommasInBind=false&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# Escape commas entered by the user when setting the authenticated user&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Useful when using simple authentication and the CN is part of the DN and contains commas, and the escaped \, is &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# pulled in as part of an LDAP sync&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# If this option is set to true it will break the default home folder provider as space names can not contain \&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.authentication.escapeCommasInUid=false&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# Comma separated list of user names who should be considered administrators by default&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.authentication.defaultAdministratorUserNames=admin&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# This flag enables use of this LDAP subsystem for user and group&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# synchronization. It may be that this subsytem should only be used for &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# authentication, in which case this flag should be set to false.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.active=true&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The authentication mechanism to use for synchronization&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.java.naming.security.authentication=simple&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The default principal to use (only used for LDAP sync)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.java.naming.security.principal=cn\=zimbra,cn\=admin,dc\=xxxx,dc\=com&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The password for the default principal (only used for LDAP sync)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.java.naming.security.credentials=xxxxxx(ldap password)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# If positive, this property indicates that RFC 2696 paged results should be&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# used to split query results into batches of the specified size. This&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# overcomes any size limits imposed by the LDAP server.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.queryBatchSize=1000&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# If positive, this property indicates that range retrieval should be used to fetch&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# multi-valued attributes (such as member) in batches of the specified size.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Overcomes any size limits imposed by Active Directory.&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.attributeBatchSize=0&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The query to select all objects that represent the groups to import.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.groupQuery=(objectclass\=groupOfNames)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The query to select objects that represent the groups to import that have changed since a certain time.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.groupDifferentialQuery=(&amp;amp;(objectclass\=groupOfNames)(!(modifyTimestamp&amp;lt;\={0})))&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The query to select all objects that represent the users to import.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.personQuery=(objectclass\=inetOrgPerson)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The query to select objects that represent the users to import that have changed since a certain time.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.personDifferentialQuery=(&amp;amp;(objectclass\=inetOrgPerson)(!(modifyTimestamp&amp;lt;\={0})))&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The group search base restricts the LDAP group query to a sub section of tree on the LDAP server.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.groupSearchBase=ou\=groups,dc\=xxxx,dc\=com&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The user search base restricts the LDAP user query to a sub section of tree on the LDAP server.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.userSearchBase=ou\=people,dc\=xxxx,dc\=com&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The name of the operational attribute recording the last update time for a group or user.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.modifyTimestampAttributeName=modifyTimestamp&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The timestamp format. Unfortunately, this varies between directory servers.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.timestampFormat=yyyyMMddHHmmss'Z'&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The attribute name on people objects found in LDAP to use as the uid in Alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.userIdAttributeName=uid&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The attribute on person objects in LDAP to map to the first name property in Alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.userFirstNameAttributeName=givenName&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The attribute on person objects in LDAP to map to the last name property in Alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.userLastNameAttributeName=sn&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The attribute on person objects in LDAP to map to the email property in Alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.userEmailAttributeName=mail&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The attribute on person objects in LDAP to map to the organizational id&amp;nbsp; property in Alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.userOrganizationalIdAttributeName=o&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The default home folder provider to use for people created via LDAP import&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.defaultHomeFolderProvider=userHomesHomeFolderProvider&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The attribute on LDAP group objects to map to the authority name property in Alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.groupIdAttributeName=cn&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The attribute on LDAP group objects to map to the authority display name property in Alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.groupDisplayNameAttributeName=mail&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The group type in LDAP&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.groupType=groupOfNames&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The person type in LDAP&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.personType=inetOrgPerson&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# The attribute in LDAP on group objects that defines the DN for its members&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.groupMemberAttributeName=member&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# If true progress estimation is enabled. When enabled, the user query has to be run twice in order to count entries.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.synchronization.enableProgressEstimation=true&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 26 Jun 2013 04:48:01 GMT</pubDate>
    <dc:creator>rakesraja</dc:creator>
    <dc:date>2013-06-26T04:48:01Z</dc:date>
    <item>
      <title>Alfresco authentication with zimbra ldap</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-authentication-with-zimbra-ldap/m-p/292150#M245280</link>
      <description>Hi,Can't able to authenticate alfresco using zimbra mail server users,it gets "Failed to login,The remote server may be unavailable or your authentication details have not been recognized",here I posted my ldap-authentication.properties file which is in&amp;nbsp; "/opt/alfresco-4.2.a/tomcat/shared/classes/al</description>
      <pubDate>Wed, 26 Jun 2013 04:48:01 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-authentication-with-zimbra-ldap/m-p/292150#M245280</guid>
      <dc:creator>rakesraja</dc:creator>
      <dc:date>2013-06-26T04:48:01Z</dc:date>
    </item>
    <item>
      <title>Re: Alfresco authentication with zimbra ldap</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-authentication-with-zimbra-ldap/m-p/292151#M245281</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;"Failed to login,The remote server may be unavailable or your authentication details have not been recognized".&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Surely, you can take a look at Zimbra logs to guess which of these two is happening.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 26 Jun 2013 18:34:12 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-authentication-with-zimbra-ldap/m-p/292151#M245281</guid>
      <dc:creator>albertocabello</dc:creator>
      <dc:date>2013-06-26T18:34:12Z</dc:date>
    </item>
    <item>
      <title>Re: Alfresco authentication with zimbra ldap</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-authentication-with-zimbra-ldap/m-p/292152#M245282</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;See if you can connect with an LDAP browser.&amp;nbsp;&amp;nbsp; That will enable you to check your principal/credentials/authentication properties are correct.&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 27 Jun 2013 09:34:51 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-authentication-with-zimbra-ldap/m-p/292152#M245282</guid>
      <dc:creator>mrogers</dc:creator>
      <dc:date>2013-06-27T09:34:51Z</dc:date>
    </item>
    <item>
      <title>Re: Alfresco authentication with zimbra ldap</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-authentication-with-zimbra-ldap/m-p/292153#M245283</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks a lot its working fine…&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 01 Jul 2013 17:34:11 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-authentication-with-zimbra-ldap/m-p/292153#M245283</guid>
      <dc:creator>rakesraja</dc:creator>
      <dc:date>2013-07-01T17:34:11Z</dc:date>
    </item>
    <item>
      <title>Re: Alfresco authentication with zimbra ldap</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-authentication-with-zimbra-ldap/m-p/292154#M245284</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am trying to authenticate against UID in LDAP authentication, same as yours. I am too facing same issue. Can you please let me know what was your issue and how did you resolve it?&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 02 Jul 2013 10:36:39 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-authentication-with-zimbra-ldap/m-p/292154#M245284</guid>
      <dc:creator>pritesh_shah17</dc:creator>
      <dc:date>2013-07-02T10:36:39Z</dc:date>
    </item>
    <item>
      <title>Re: Alfresco authentication with zimbra ldap</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/alfresco-authentication-with-zimbra-ldap/m-p/292155#M245285</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am just changing the correct principal/credentials/authentication values in the ldap-authentication.properties file&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 24 Jul 2013 05:18:41 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/alfresco-authentication-with-zimbra-ldap/m-p/292155#M245285</guid>
      <dc:creator>rakesraja</dc:creator>
      <dc:date>2013-07-24T05:18:41Z</dc:date>
    </item>
  </channel>
</rss>

