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.
ERROR [org.alfresco.fileserver] Failed to get local domain/workgroup name, using default of WORKGROUP ERROR [org.alfresco.fileserver] (This may be due to firewall settings or incorrect <broadcast> setting)
You will get NTLM SSO and CIFS authentication against the domain server by default.
smbclient \\\\localname\\alfresco -U user_from_ad
I would suggest an authentication chain containing the passthru subsystem for authentication and the ldap-ad subsystem for synchronization. You will get NTLM SSO and CIFS authentication against the domain server by default.Just set the following in alfresco-global.propertiesauthentication.chain=passthru1assthru,ldap1:ldap-adldap.authentication.active=falsepassthru.authentication.domain=# Intentionally left blankpassthru.authentication.servers=DOMAIN\\domaincontroller.com,domaincontroller.compassthru.authentication.defaultAdministratorUserNames=Administratorldap.authentication.java.naming.provider.url=ldap://domaincontroller.com:389ldap.synchronization.java.naming.security.principal=alfresco@domainldap.synchronization.java.naming.security.credentials=secretldap.synchronization.groupSearchBase=ou=Security Groups,ou=Alfresco,dc=domainldap.synchronization.userSearchBase=ou=User Accounts,ou=Alfresco,dc=domainI would recommend taking a v3.3 nightly build or building from HEAD, as a number of improvements have been made since the v3.2 Community release.See http://wiki.alfresco.com/wiki/Alfresco_Authentication_Subsystems for a guide to all these parameters and their meanings.
ldap.synchronization.java.naming.security.principal=alfresco@domain passthru.authentication.defaultAdministratorUserNames=Administrator