08-01-2010 11:16 AM
passthru.authentication.sso.enabled=flase
passthru.authentication.useLocalServer=false
passthru.authentication.domain=
# (domain specific property): NetBIOS name of your domain and
# domain controller.s IP address, add more separated by commas
#passthru.authentication.servers=DOMAIN\\192.168.0.1,192.168.0.1
passthru.authentication.servers=intra\\xx.xx.xx.xx,xx.xx.xx.xx
passthru.authentication.guestAccess=false
passthru.authentication.defaultAdministratorUserNames=administrator,Administrator
passthru.authentication.connectTimeout=5000
passthru.authentication.offlineCheckInterval=300
passthru.authentication.protocolOrder=TCPIP,,NETBIOS
ntlm.authentication.sso.enabled=false
alfresco.authentication.allowGuestLogin=false
ntlm.authentication.mapUnknownUserToGuest=false
passthru.authentication.authenticateCIFS=true
passthru.authentication.authenticateFTP=false
# Authenticaton AD
#————————–
#authentication.chain=passthru1:passthru,ldap-ad1:ldap-ad
authentication.chain=passthru1:passthru
# Doamin mapping
#————-
filesystem.domainMappings=intra
filesystem.domainMappings.value.intra.subnet=192.168.2.0
filesystem.domainMappings.value.intra.mask=192.168.2.255
cifs.enabled=true
# (domain specific property): change to match alfresco hostname + ‘A’
cifs.serverName=dmsA
#cifs.serverName=192.168.2.142
#cifs.serverName=${localname}
# (domain specific property): NetBIOS domain name
cifs.domain=intra
cifs.hostannounce=true
cifs.sessionTimeout=900
# (domain specific property): network broadcast address
cifs.broadcast=192.168.2.255
#cifs.broadcast=255.255.255.0
#cifs.tcpipSMB.port=1445
#cifs.ipv6.enabled=false
#cifs.nerBIOSSMB.namePort=1137
#cifs.nerBIOSSMB.datagramPort=1138
#cifs.nerBIOSSMB.sessionPort=1139
# (domain specific property): change to match alfresco hostname
#cifs.urlfile.prefix=http://hostname:8080/alfresco/
cifs.urlfile.prefix=http://192.168.2.142:8080/alfresco/
09-16-2010 06:22 AM
11-18-2010 09:35 AM
02-04-2018 09:16 AM
Hey Guys,
At my current site we are using Alfresco 3.4d community edition. The issue which took place was that we were unable to login properly from the Alfresco plugin in Moodle. It turned out that this particular error was a result of the clock being off on the Moodle server. The clock on Moodle was roughly six and a half minutes behind the Alfresco server (which was the real time). The moment that we updated the clock on the Moodle server it started working again.
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.