nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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.

Ldap and Cifs

janvg

Is it true that if we enable LDAP authentication and synchronisation on 1.4 CIFS will not work ? Or are we missing something in the setup ?

Find more posts tagged with

Comments

andy

Hi

Yes and No.

CIFS can try and use the authentication component wired up in Alfresco.
The LDAP version can not support CIFS - it would have to be able to get hold of the MD4 hash for the password.

CIFS can go direct to Active Directory to validate kerberos tickets So CIFS and LDAP can work together with Active Directory.

Regards

Andy

rdanner

Hi

Yes and No.

CIFS can try and use the authentication component wired up in Alfresco.
The LDAP version can not support CIFS - it would have to be able to get hold of the MD4 hash for the password.

CIFS can go direct to Active Directory to validate kerberos tickets So CIFS and LDAP can work together with Active Directory.

Regards

Andy

Andy can you use chaining/referal to solve for something like this? where Alfresco goes to a single LDAP and that LDAP goes after that value pair from AD?

OR can the CIFS implementation use a combo of authentication solutions IE go to AD first, if it cant find the DN there look to the second source?

Lastly if the MD4 has was in the LDAP server would there be an issue? I think a product like centrify may be able to push the hashed password out to the LDAP

any of the above would work for me but I dont have any idea if any of them are possible.

andy

Hi

The chaining authentication does not handle CIFS and MD4 hashes at the moment. It could find the first implementation that supports MD4 and report that hash. CIFS only tries agaisnt one hash.

An LDAP implementation could provide the MD4 hash …. but do you want to make password hashes readable by anyone/guest from your LDAP server (as you have not authenticated when you need to go and get them - or you would need to use the default ldap username and credentials). It is possible to implement the appropriate methods on top of the LDAP auth impl if you want.

The only other alternative is to keep hashes after people log in (in memory or persisted). But this requires a good login to build the cache (CIFS access only is not allowed) and the potential for the hash to go out of sync.

Overall it is best if CIFS can validate a Kerberos ticket at the moment.
It could useMD4 hash (from plain text would be possible) + NTLM, Kerberos, NTLM passthrough.

It is possible we could support Kerberos against other kerberos servers but I do not know the details here.

Basically NTLM is a bit of a pain.

Regards

Andy