<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: LDAP and CIFS not working together in Alfresco Archive</title>
    <link>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16124#M7123</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;CIFS can now authenticate direct to active deirectoty using kerberos.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You could use LDAP, or Kerberos to authenticate against the same AD server.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 03 Oct 2006 09:56:58 GMT</pubDate>
    <dc:creator>andy</dc:creator>
    <dc:date>2006-10-03T09:56:58Z</dc:date>
    <item>
      <title>LDAP and CIFS not working together</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16118#M7117</link>
      <description>Hi, yet another LDAP releated problem…We configured Alfresco to authenticate with Active Directory, wasn't easy but it works now… almost.Authentication in the web client is working fine but CIFS fails horribly. CIFS works like expected when the LDAP authentication isn't used but when we enable the L</description>
      <pubDate>Tue, 02 May 2006 15:28:20 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16118#M7117</guid>
      <dc:creator>simon</dc:creator>
      <dc:date>2006-05-02T15:28:20Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP and CIFS not working together</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16119#M7118</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Simon&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The current CIFS code requires an MD4 password hash to work or the NTLM passthrough authentication component.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;This is just how NTLM authentication chit-chit-chat works.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The LDAP authentication does not have this information to hand.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;(Windows has it sneeked away or uses some other mechanism such as Kerberos) This is the only reason we use MD4 password hashes.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The situation is covered in the authentication docs.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;NTLM authentication would work with CIFS and SingleSignOn, but it can not go against multiple servers, nor is it being updated as part of the CIFS upgrades. You could chain them together but CIFS does not do similar chaining yet. I have raised this with our CIFS expert.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Work is active to support the more advanced options for CIFS authentication. Here are the quotes….&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;The new CIFS authenticator can use MD4 hashes if the auth component supports it, that allows the client to use NTLMv1 or v2, and/or also do kerberos to AD, depending on what the client decides to do.&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;BLOCKQUOTE class="jive-quote"&gt;A Windows domain workstation will use kerberos whereas a non-domain client tends to use NTLMv2, also tested with Mac OSX, that used NTLMv2&lt;/BLOCKQUOTE&gt;&lt;BR /&gt;&lt;SPAN&gt;It would be possible to store MD4 hashes in memory for people who had previously authenticated against the repo….then use these.&amp;nbsp; You must have logged in at least one to the repo to use CIFS. Would this do? I have no other ideas here …&amp;nbsp; &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Hope this explains it.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 May 2006 16:19:52 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16119#M7118</guid>
      <dc:creator>andy</dc:creator>
      <dc:date>2006-05-04T16:19:52Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP and CIFS not working together</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16120#M7119</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Thanks Andy!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So there are 2 different sollutions here: NTLM or MD4 hashing. The NTLM authentication solves the MD4 hashing as I understand from &lt;/SPAN&gt;&lt;A href="http://wiki.alfresco.com/wiki/Image:ServerAuthArch.gif" rel="nofollow noopener noreferrer"&gt;your schema&lt;/A&gt;&lt;SPAN&gt;, correct?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;NTLM is a problem for some reasons in our current setup (no login page to show messages, problems with our OpenLDAP authentication,…) so I would like to solve the MD4 hashing problem without using NTLM. Is this possible?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;How do I use MD4 hashing for the CIFS interface?!&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Would be nice to have it up and running before the weekend.&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 May 2006 21:07:08 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16120#M7119</guid>
      <dc:creator>simon</dc:creator>
      <dc:date>2006-05-04T21:07:08Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP and CIFS not working together</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16121#M7120</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi Simon&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The diagram shows how it will be ….&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;CIFS uses NTLM/NTLMv2/Kerberos under the hood.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;It has its own authentication dialog between the client and our own CIFS server code.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;For an authentication service to fit in with current CIFS authentication it has to provide passthrough NTLM support or be able to provide the MD4 password hash. This is then used between our server and the CIFS client in the authentication protocol. &lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;So how can LDAP in general get the MD4 password hash given a user name? &lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;The answer is it can not.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;There are two special cases - one that the password is in plain text or it is already MD4 hashed. This latter is how our base authentication service supports CIFS. The NTLM authentication component does real NTLM auth. by pass through to the real thing.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You will not be able to use CIFS with LDAP and the current release.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Simply due to the MD4 password issue. We do not support the two special cases above in the LDAP authentication.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;What I was going on about (without enough background) in the previous post is …..&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;It is possible that as users login (and we know the password is correct) we could cache the MD4 hash of the password, and make this available for CIFS. So in effect, all authentication components could support CIFS regardless of what happens underneath. This would require code changes and the user would have to log into the repo once before they could use CIFS - which would be a bit odd.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;The next release of the CIFS server may not have this restriction for clients that support Kerberos tickets, but as I understand it NTLM and NTLMv2 will still need to get hold of the MD4 hash.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I hope this explains the situation&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 05 May 2006 10:49:09 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16121#M7120</guid>
      <dc:creator>andy</dc:creator>
      <dc:date>2006-05-05T10:49:09Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP and CIFS not working together</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16122#M7121</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I am getting this same few errors, but I don't believe I'm using the CIFS syste. (I haven't rename file-servers-custom.xml.sample to .xml)&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;I am using LDAP, and the bottom three messages on this trace are the issue.&amp;nbsp; Notice the first two lines as well, as these may be related.&amp;nbsp; Can this issue come up if I'm not using the file-servers-custom.xml file?&amp;nbsp; Is the license error related?&amp;nbsp;&amp;nbsp; We are using a valid enterprise version 1.3 of alfresco, but I have always seen this error.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;13:16:54,080 WARN&amp;nbsp; [DescriptorService] Alfresco license: Failed to verify license - Invalid License!&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;13:16:54,081 WARN&amp;nbsp; [DescriptorService] Alfresco license: Restricted Alfresco Repository to read-only capability&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;13:16:54,082 INFO&amp;nbsp; [RAMJobStore] RAMJobStore initialized.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;13:16:54,082 INFO&amp;nbsp; [StdSchedulerFactory] Quartz scheduler 'LicenseVerifier' initialized from an externally provided properties instance.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;13:16:54,082 INFO&amp;nbsp; [StdSchedulerFactory] Quartz scheduler version: 1.4.5&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;13:16:54,087 INFO&amp;nbsp; [QuartzScheduler] Scheduler LicenseVerifier_$_NON_CLUSTERED started.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;13:16:54,397 INFO&amp;nbsp; [PatchExecuter] Checking for patches to apply …&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;13:16:54,454 INFO&amp;nbsp; [PatchExecuter] No patches were required.&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;13:16:54,541 INFO&amp;nbsp; [ContentDiskDriver] Locked files will be marked as offline&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;13:16:54,578 ERROR [protocol] Failed to get local domain/workgroup name, using default of WORKGROUP&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;13:16:54,578 ERROR [protocol] (This may be due to firewall settings or incorrect &amp;lt;broadcast&amp;gt; setting)&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;13:16:54,588 ERROR [org.alfresco.smb.protocol] File server configuration error, Wrong authentication setup for alfresco authenticator&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 09 Aug 2006 20:26:33 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16122#M7121</guid>
      <dc:creator>eron123</dc:creator>
      <dc:date>2006-08-09T20:26:33Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP and CIFS not working together</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16123#M7122</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;I was wondering if anyone at Alfresco (or other) could comment on the status of these proposed authentication changes.&amp;nbsp; We are having the same issue with trying to enable CIFS server when using LDAP for authenticator.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Are these new proposed changes supported by the upcoming 1.4?&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Thanks-&lt;/SPAN&gt;&lt;BR /&gt;&lt;SPAN&gt;Hans&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 02 Oct 2006 21:32:22 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16123#M7122</guid>
      <dc:creator>hansasi</dc:creator>
      <dc:date>2006-10-02T21:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: LDAP and CIFS not working together</title>
      <link>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16124#M7123</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;SPAN&gt;Hi&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;CIFS can now authenticate direct to active deirectoty using kerberos.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;You could use LDAP, or Kerberos to authenticate against the same AD server.&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Regards&lt;/SPAN&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;SPAN&gt;Andy&lt;/SPAN&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 03 Oct 2006 09:56:58 GMT</pubDate>
      <guid>https://connect.hyland.com/t5/alfresco-archive/ldap-and-cifs-not-working-together/m-p/16124#M7123</guid>
      <dc:creator>andy</dc:creator>
      <dc:date>2006-10-03T09:56:58Z</dc:date>
    </item>
  </channel>
</rss>

