<?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 Open Ldap y Alfresco 4.2.c in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/open-ldap-y-alfresco-4-2-c/m-p/179576#M132706</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Saludos amigos, he instalado Alfresco 4.2.c he intentado configurarlo para tener acceso desde mis usuarios en servidor OpenLdap pero ningún resultado positivo, he leido por internet los cambios y agregados a los archivos alfresco-global.properties y ldap-authentication.properties&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Les muestro como tengo mi archivo alfresco-global.properties sin cambios para que por favor me ayuden concretamente que debo hacer en el y muchas gracias por toda la ayuda que puedan prestarme amigos.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;###############################&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;## Common Alfresco Properties #&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;###############################&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Sample custom content and index data location&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#dir.root=/srv/alfresco/alf_data&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#dir.keystore=${dir.root}/keystore&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Sample database connection properties&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.username=alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.password=alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# External locations&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#————-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#ooo.exe=soffice&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#ooo.enabled=false&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#jodconverter.officeHome=./OpenOffice.org&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#jodconverter.portNumbers=8101&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#jodconverter.enabled=true&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#img.root=./ImageMagick&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#swf.exe=./bin/pdf2swf&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Property to control whether schema updates are performed automatically.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Updates must be enabled during upgrades as, apart from the static upgrade scripts,&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# there are also auto-generated update scripts that will need to be executed.&amp;nbsp; After&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# upgrading to a new version, this can be disabled.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.schema.update=true&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# MySQL connection&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.driver=org.gjt.mm.mysql.Driver&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.url=jdbc:mysql://localhost/alfresco?useUnicode=yes&amp;amp;characterEncoding=UTF-8&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Oracle connection&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.driver=oracle.jdbc.OracleDriver&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.url=jdbc&lt;img id="smileysurprised" class="emoticon emoticon-smileysurprised" src="https://connect.hyland.com/i/smilies/16x16_smiley-surprised.png" alt="Smiley Surprised" title="Smiley Surprised" /&gt;racle:thin:@localhost:1521:alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# SQLServer connection&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Requires jTDS driver version 1.2.5 and SNAPSHOT isolation mode&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Enable TCP protocol on fixed port 1433&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Prepare the database with:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# ALTER DATABASE alfresco SET ALLOW_SNAPSHOT_ISOLATION ON;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.driver=net.sourceforge.jtds.jdbc.Driver&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.url=jdbc:jtds:sqlserver://localhost:1433/alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.txn.isolation=4096&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# PostgreSQL connection (requires postgresql-8.2-504.jdbc3.jar or equivalent)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.driver=org.postgresql.Driver&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.url=jdbc&lt;img id="smileytongue" class="emoticon emoticon-smileytongue" src="https://connect.hyland.com/i/smilies/16x16_smiley-tongue.png" alt="Smiley Tongue" title="Smiley Tongue" /&gt;ostgresql://localhost:5432/alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# DB2 connection&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.driver=com.ibm.db2.jcc.DB2Driver&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#db.url=jdbc:db2://localhost:50000/alfresco:retrieveMessagesFromServerOnGetMessage=true;&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Index Recovery Mode&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#————-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#index.recovery.mode=AUTO&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Outbound Email Configuration&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#————-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#mail.host=&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#mail.port=25&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#mail.username=anonymous&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#mail.password=&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#mail.encoding=UTF-8&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;&lt;A class="jive-link-email-small" href="mailto:#mail.from.default=alfresco@alfresco.org" rel="nofollow noopener noreferrer"&gt;#mail.from.default=alfresco@alfresco.org&lt;/A&gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#mail.smtp.auth=false&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Alfresco Email Service and Email Server&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#————-&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# Enable/Disable the inbound email service.&amp;nbsp; The service could be used by processes other than&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# the Email Server (e.g. direct RMI access) so this flag is independent of the Email Service.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#————-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#email.inbound.enabled=true&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# Email Server properties&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#————-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#email.server.enabled=true&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#email.server.port=25&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#email.server.domain=alfresco.com&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#email.inbound.unknownUser=anonymous&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# A comma separated list of email REGEX patterns of allowed senders.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# If there are any values in the list then all sender email addresses&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# must match. For example:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&amp;nbsp;&amp;nbsp; .*\@alfresco\.com, .*\@alfresco\.org&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Allow anyone:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#————-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#email.server.allowed.senders=.*&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# The default authentication chain&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# To configure external authentication subsystems see:&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# &lt;/SPAN&gt;&lt;A href="http://wiki.alfresco.com/wiki/Alfresco_Authentication_Subsystems" rel="nofollow noopener noreferrer"&gt;http://wiki.alfresco.com/wiki/Alfresco_Authentication_Subsystems&lt;/A&gt;&lt;BR /&gt;&lt;SPAN&gt;#————-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;authentication.chain=alfrescoNtlm1:alfrescoNtlm,ldap:ldap&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# URL Generation Parameters (The ${localname} token is replaced by the local server name)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#————-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#alfresco.context=alfresco&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#alfresco.host=${localname}&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#alfresco.port=8080&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#alfresco.protocol=http&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#share.context=share&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#share.host=${localname}&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#share.port=8080&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#share.protocol=http&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#imap.server.enabled=true&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#imap.server.port=143&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#imap.server.host=localhost&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# Default value of alfresco.rmi.services.host is 0.0.0.0 which means 'listen on all adapters'.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# This allows connections to JMX both remotely and locally.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;alfresco.rmi.services.host=0.0.0.0&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# RMI service ports for the individual services.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# These seven services are available remotely.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Assign individual ports for each service for best performance&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# or run several services on the same port. You can even run everything on 50500 if needed.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;# Select 0 to use a random unused port.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#avm.rmi.service.port=50501&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#avmsync.rmi.service.port=50502&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#attribute.rmi.service.port=50503&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#authentication.rmi.service.port=50504&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#repo.rmi.service.port=50505&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#action.rmi.service.port=50506&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#wcm-deployment-receiver.rmi.service.port=50507&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#monitor.rmi.service.port=50508&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;lt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&amp;gt;&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ESTE ES MI ARCHIVO ldap-authentication.properties&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 definit$&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;#&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.authentication.allowGuestLogin=true&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 wi$&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$&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=&lt;/SPAN&gt;&lt;BR /&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://openldap.domain.com:389&lt;/SPAN&gt;&lt;BR /&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;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=administrador&lt;/SPAN&gt;&lt;BR /&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=false&lt;/SPAN&gt;&lt;BR /&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\=Manager,dc\=company,dc\=com&lt;/SPAN&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=secret&lt;/SPAN&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=0&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.&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\=company,dc\=com&lt;/SPAN&gt;&lt;BR /&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\=company,dc\=com&lt;/SPAN&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;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;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.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=largeHomeFolderProvider&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=description&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;BR /&gt;&lt;SPAN&gt;ldap.synchronization.enableProgressEstimation=true&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;# Requests timeout, in miliseconds, use 0 for none (default)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;ldap.authentication.java.naming.read.timeout=0&lt;/SPAN&gt;&lt;BR /&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 22 Mar 2014 17:40:54 GMT</pubDate>
    <dc:creator>jvillafranca83</dc:creator>
    <dc:date>2014-03-22T17:40:54Z</dc:date>
    <item>
      <title>Open Ldap y Alfresco 4.2.c</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/open-ldap-y-alfresco-4-2-c/m-p/179576#M132706</link>
      <description>Saludos amigos, he instalado Alfresco 4.2.c he intentado configurarlo para tener acceso desde mis usuarios en servidor OpenLdap pero ningún resultado positivo, he leido por internet los cambios y agregados a los archivos alfresco-global.properties y ldap-authentication.propertiesLes muestro como ten</description>
      <pubDate>Sat, 22 Mar 2014 17:40:54 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/open-ldap-y-alfresco-4-2-c/m-p/179576#M132706</guid>
      <dc:creator>jvillafranca83</dc:creator>
      <dc:date>2014-03-22T17:40:54Z</dc:date>
    </item>
    <item>
      <title>Re: Open Ldap y Alfresco 4.2.c</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/open-ldap-y-alfresco-4-2-c/m-p/179577#M132707</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Buenas.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;¿Puedes revisar que nos hayas puesto correctamente el alfresco-global.properties? Está todo comentado (con almohadillas por delante). A ver si le echamos un vistazo y te comentamos.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Un saludo.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 22 Mar 2014 18:08:07 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/open-ldap-y-alfresco-4-2-c/m-p/179577#M132707</guid>
      <dc:creator>cristinamr</dc:creator>
      <dc:date>2014-03-22T18:08:07Z</dc:date>
    </item>
  </channel>
</rss>

