topic Re: Alfresco 3.2 broken LDAP sync in Alfresco Archive https://connect.hyland.com/t5/alfresco-archive/alfresco-3-2-broken-ldap-sync/m-p/225247#M178377 <HTML><HEAD></HEAD><BODY><SPAN>We like our users. It's just we are busy people.</SPAN><BR /><BR /><SPAN>There were actually configurable properties errorOnMissingUID and errorOnMissingGID on the userRegistry bean that you could have overridden in the extension classpath. However, I agree that the default behaviour should be that we don't abort if UIDs or GIDs are missing. So I've checked in a change that should show up in the next nightly build.</SPAN></BODY></HTML> Fri, 17 Jul 2009 12:20:58 GMT dward 2009-07-17T12:20:58Z Alfresco 3.2 broken LDAP sync https://connect.hyland.com/t5/alfresco-archive/alfresco-3-2-broken-ldap-sync/m-p/225245#M178375 So I've been trying to configure my 3.2 users and groups LDAP synchronization (I use AD). So far it was good, hats off on the new configuration subsystems. However, I'm stuck with some bizarre error which I didn't have with Alfresco 3.1, with the exact same configuration parameters and same AD.All u Thu, 09 Jul 2009 19:24:38 GMT https://connect.hyland.com/t5/alfresco-archive/alfresco-3-2-broken-ldap-sync/m-p/225245#M178375 fo1337 2009-07-09T19:24:38Z Re: Alfresco 3.2 broken LDAP sync https://connect.hyland.com/t5/alfresco-archive/alfresco-3-2-broken-ldap-sync/m-p/225246#M178376 <HTML><HEAD></HEAD><BODY><SPAN>Nobody likes me :'(</SPAN><BR /><BR /><SPAN>I've posted a bug report as I suspect it is one… </SPAN><A href="https://issues.alfresco.com/jira/browse/ALFCOM-3193" rel="nofollow noopener noreferrer">https://issues.alfresco.com/jira/browse/ALFCOM-3193</A></BODY></HTML> Fri, 10 Jul 2009 13:54:58 GMT https://connect.hyland.com/t5/alfresco-archive/alfresco-3-2-broken-ldap-sync/m-p/225246#M178376 fo1337 2009-07-10T13:54:58Z Re: Alfresco 3.2 broken LDAP sync https://connect.hyland.com/t5/alfresco-archive/alfresco-3-2-broken-ldap-sync/m-p/225247#M178377 <HTML><HEAD></HEAD><BODY><SPAN>We like our users. It's just we are busy people.</SPAN><BR /><BR /><SPAN>There were actually configurable properties errorOnMissingUID and errorOnMissingGID on the userRegistry bean that you could have overridden in the extension classpath. However, I agree that the default behaviour should be that we don't abort if UIDs or GIDs are missing. So I've checked in a change that should show up in the next nightly build.</SPAN></BODY></HTML> Fri, 17 Jul 2009 12:20:58 GMT https://connect.hyland.com/t5/alfresco-archive/alfresco-3-2-broken-ldap-sync/m-p/225247#M178377 dward 2009-07-17T12:20:58Z