<?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: Active Directory LDAP authentication in Network and Storage Protocols</title>
    <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Active-Directory-LDAP-authentication/m-p/57939#M5357</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Reviving this to see if anyone has found a workaround to this very annoying issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You cannot log into the SP using a Domain account.&amp;nbsp; This is documented by NetApp that it must be a local account and verified at customers and our labs.&amp;nbsp; This makes sense because the SP is not running CIFS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone found a solution to let you log into the "system console" either from the SP, or physically connected to the back of the controller using a AD domain account?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is assuming CIFS is running, and the user can log into the filer via SSH using an AD domain account.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This leaves customers that are subject to audits in a very difficult place because it undermines all RBAC when physical connectivity is required.&amp;nbsp; Even though DFM makes it easier, maintaining local user accounts in large enterprises is not acceptable in my opinion.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 11 Jul 2012 00:32:22 GMT</pubDate>
    <dc:creator>audifreakjim</dc:creator>
    <dc:date>2012-07-11T00:32:22Z</dc:date>
    <item>
      <title>Active Directory LDAP authentication</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Active-Directory-LDAP-authentication/m-p/57919#M5353</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt; &lt;BR /&gt;Can I use AD domain user a/c to login filer console to manage filer through AD LDAP authentication?&lt;/P&gt;&lt;P&gt; &lt;BR /&gt; &lt;BR /&gt;Regards&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 07:04:07 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Active-Directory-LDAP-authentication/m-p/57919#M5353</guid>
      <dc:creator>tatlee</dc:creator>
      <dc:date>2025-06-05T07:04:07Z</dc:date>
    </item>
    <item>
      <title>Re: Active Directory LDAP authentication</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Active-Directory-LDAP-authentication/m-p/57924#M5354</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You certanly can. Run "cifs setup" from the command line. And dont worry if you dont have a cifs license as its not a requirement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-C- &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Dec 2010 05:10:33 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Active-Directory-LDAP-authentication/m-p/57924#M5354</guid>
      <dc:creator>cory_mckee</dc:creator>
      <dc:date>2010-12-02T05:10:33Z</dc:date>
    </item>
    <item>
      <title>Re: Active Directory LDAP authentication</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Active-Directory-LDAP-authentication/m-p/57929#M5355</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;thanks cory.mckee&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;but on cifs setup, I have choose the option (1) Active Directory domain authentication.&lt;/P&gt;&lt;P&gt;Also I configure the options of ldap&lt;/P&gt;&lt;P&gt;ldap.ADdomain XXX.XXX.COM&lt;/P&gt;&lt;P&gt;ldap.base&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; cn=group,dc=xxx,dc=xxx,dc=com&lt;/P&gt;&lt;P&gt;ldap.name&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; service a/c name&lt;/P&gt;&lt;P&gt;ldap.passwd&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; userpasswd&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can these settings satisfy to login console use AD ldap authentication?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards,&lt;/P&gt;&lt;P&gt;Terrence Lee&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Dec 2010 06:04:58 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Active-Directory-LDAP-authentication/m-p/57929#M5355</guid>
      <dc:creator>tatlee</dc:creator>
      <dc:date>2010-12-02T06:04:58Z</dc:date>
    </item>
    <item>
      <title>Re: Active Directory LDAP authentication</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Active-Directory-LDAP-authentication/m-p/57934#M5356</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;From a login perspective you need to assign the account to a group on your filer using the useradmin command&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;useradmin domainuser add &amp;lt;user_name&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; -g &amp;lt;group1&amp;gt;[,&amp;lt;group2&amp;gt;,...,&amp;lt;groupN&amp;gt;]&lt;BR /&gt;useradmin domainuser delete &amp;lt;user_name&amp;gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; -g &amp;lt;group1&amp;gt;[,&amp;lt;group2&amp;gt;,...,&amp;lt;groupN&amp;gt;]&lt;BR /&gt;useradmin domainuser list -g &amp;lt;group_name&amp;gt;&lt;BR /&gt;useradmin domainuser load &amp;lt;filename&amp;gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 02 Dec 2010 16:05:17 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Active-Directory-LDAP-authentication/m-p/57934#M5356</guid>
      <dc:creator>cory_mckee</dc:creator>
      <dc:date>2010-12-02T16:05:17Z</dc:date>
    </item>
    <item>
      <title>Re: Active Directory LDAP authentication</title>
      <link>https://community.netapp.com/t5/Network-and-Storage-Protocols/Active-Directory-LDAP-authentication/m-p/57939#M5357</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Reviving this to see if anyone has found a workaround to this very annoying issue.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You cannot log into the SP using a Domain account.&amp;nbsp; This is documented by NetApp that it must be a local account and verified at customers and our labs.&amp;nbsp; This makes sense because the SP is not running CIFS.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Has anyone found a solution to let you log into the "system console" either from the SP, or physically connected to the back of the controller using a AD domain account?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This is assuming CIFS is running, and the user can log into the filer via SSH using an AD domain account.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;This leaves customers that are subject to audits in a very difficult place because it undermines all RBAC when physical connectivity is required.&amp;nbsp; Even though DFM makes it easier, maintaining local user accounts in large enterprises is not acceptable in my opinion.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 11 Jul 2012 00:32:22 GMT</pubDate>
      <guid>https://community.netapp.com/t5/Network-and-Storage-Protocols/Active-Directory-LDAP-authentication/m-p/57939#M5357</guid>
      <dc:creator>audifreakjim</dc:creator>
      <dc:date>2012-07-11T00:32:22Z</dc:date>
    </item>
  </channel>
</rss>

