topic CIFS + Kerberos working at Enterprise 3.2, but not at Comm in Alfresco Archive

CIFS + Kerberos working at Enterprise 3.2, but not at Comm

claudio_martins — Sun, 17 Jan 2010 18:27:52 GMT

Hello there,I've been during all last week trying to get Alfresco Community 3.2 to work with Kerberos based authentication for our company across all OS clients available, and as many other people here at the forums and at Alfresco's Jira, I wasn't successful from Windows 2003 Server and all other v

Re: CIFS + Kerberos working at Enterprise 3.2, but not at Comm

mikeh — Sun, 17 Jan 2010 19:47:12 GMT

There's been a longer than usual delay for code being merged from v3.2 Enterprise to HEAD because of the large changes on HEAD surrounding the Spring SURF migration.

Merging from V3.2 to HEAD has now started, so I would expect this issue to be fixed in the next few days/weeks - certainly by v3.3 final.

Thanks,
Mike

Re: CIFS + Kerberos working at Enterprise 3.2, but not at Comm

claudio_martins — Mon, 18 Jan 2010 12:21:08 GMT

Hi Mike, thanks a lot for your reply.

Is there any chance we can know exactly which changes to the code were made to make it work? Or was it too many things to list here?

Do you have any idea on when 3.3 Community will be released?

Cheers, CM.

Re: CIFS + Kerberos working at Enterprise 3.2, but not at Comm

mikeh — Mon, 18 Jan 2010 12:43:53 GMT

Here's the svn diff for the ticket:

Index: projects/repository/source/java/org/alfresco/filesys/auth/cifs/EnterpriseCifsAuthenticator.java
===================================================================
— projects/repository/source/java/org/alfresco/filesys/auth/cifs/EnterpriseCifsAuthenticator.java   (revision 17358)
+++ projects/repository/source/java/org/alfresco/filesys/auth/cifs/EnterpriseCifsAuthenticator.java   (revision 17359)
@@ -754,7 +754,7 @@
         
         boolean loggedOn = false;
         
-        if ( useRawNTLMSSP() || isNTLMSSP == true || sess.hasSetupObject( client.getProcessId()) || setupObj != null)
+        if ( respBlob != null || sess.hasSetupObject( client.getProcessId()) || setupObj != null)
         {
             //  NTLMSSP has two stages, if there is a stored setup object then indicate more processing
             //  required
‍‍‍‍‍‍‍‍‍‍‍‍‍‍

Note: You're welcome to try with just this change; I've no idea if modifications elsewhere are also required.

Thanks,
Mike

Re: CIFS + Kerberos working at Enterprise 3.2, but not at Comm

claudio_martins — Tue, 19 Jan 2010 13:51:43 GMT

Hi Mike, that really worked! You rock!

I have successfully tested this correction for the following clients: XP, 2003, Vista, W7, Linux RedHat/Debian and MacOS X 10.6.

Cheers, CM.