11-30-2010 09:09 PM
#
# AD configuration
#
authentication.chain=alfrescoNtlm1:alfrescoNtlm,ldap-ad1:ldap-ad,ldap-ad2:ldap-ad,ldap-ad3:ldap-ad
synchronization.synchronizeChangesOnly=true
synchronization.syncOnStartup=false
synchronization.import.cron=0 30 2 * * ?
ldap.authentication.active=true
# synchronization.synchronizeChangesOnly=true
# synchronization.syncOnStartup=false
ldap.authentication.java.naming.security.authentication=simple
# Change here OU=Staff or OU=Student or OU=External
ldap.authentication.userNameFormat=CN=%s,OU=Staff,OU=Accounts,DC=AD,DC=MY,DC=ORG
ldap.authentication.allowGuestLogin=true
ldap.authentication.java.naming.provider.url=ldap://ad1.ad.my.org:389
ldap.authentication.defaultAdministratorUserNames=lkolnz,swelsd,anbeitz
ldap.authentication.escapeCommasInBind=true
ldap.authentication.escapeCommasInUid=true
ldap.synchronization.active=true
ldap.synchronization.java.naming.security.principal=CN=lkolnz,OU=Staff,OU=Accounts,DC=AD,DC=MY,DC=ORG
ldap.synchronization.java.naming.security.credentials=secret_password
ldap.synchronization.queryBatchSize=500
ldap.synchronization.attributeBatchSize=100
ldap.synchronization.groupQuery=(&(objectclass=group)(objectCategory=Group))
ldap.synchronization.groupDifferentialQuery=(&(objectclass=group)(!(whenChanged<={0})))
ldap.synchronization.groupMemberAttributeName=member
ldap.synchronization.groupIdAttributeName=cn
ldap.synchronization.groupType=group
ldap.synchronization.groupSearchBase=OU=Groups,DC=AD,DC=MY,DC=ORG
ldap.synchronization.personQuery=(&(objectCategory=Person)(sAMAccountName=*))
ldap.synchronization.personDifferentialQuery=(&(objectclass=user)(!(whenChanged<={0})))
# Change here OU=Staff or OU=Student or OU=External
ldap.synchronization.userSearchBase=OU=Staff,OU=Accounts,DC=AD,DC=MY,DC=ORG
ldap.synchronization.modifyTimestampAttributeName=whenChanged
ldap.synchronization.timestampFormat=yyyyMMddHHmmss'.0Z'
ldap.synchronization.userIdAttributeName=sAMAccountName
ldap.synchronization.userFirstNameAttributeName=givenName
ldap.synchronization.userLastNameAttributeName=sn
ldap.synchronization.userEmailAttributeName=mail
#ldap.synchronization.userOrganizationalIdAttributeName=
ldap.synchronization.defaultHomeFolderProvider=userHomesHomeFolderProvider
ldap.synchronization.personType=user
12-03-2010 09:27 AM
Would setting "ldap.synchronization.active=false" preserve all current users and their files?From my experience i think so, I'm quite sure, but make a test to preproduction deployment just in case.
Is it the only change I need to do?Probably, although you might need to make sure that "synchronization.autoCreatePeopleOnLogin" is set to true so that new user's homes are created automatically. I suppose that this will work even if you have no synchronization activated in your chain, but never tried it myself.
Any other advice?If you have an Active Directory consider just using passthru subsystem.
12-08-2010 11:59 PM
12-13-2010 09:58 AM
12-14-2010 07:21 PM
I would create a very simple JavaScript in Data Dictionary/scripts repository folder that executed against a folder (User homes in this case) iterates all its children and checks if they are of folder type and if they are empty. If they are empty just delete it.
If by chance some of the deleted home's are for valid users that shouldn't be such a big deal, after all the home will be created again next time they log in.
After checking that everything is alright you might want to empty the Trashcan.
03-27-2011 09:03 PM
Tags
Find what you came for
We want to make your experience in Hyland Connect as valuable as possible, so we put together some helpful links.