<?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: NetApp LDAP hashes in ONTAP Discussions</title>
    <link>https://community.netapp.com/t5/ONTAP-Discussions/NetApp-LDAP-hashes/m-p/10200#M2341</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes I can confirm that CRYPT will work!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would love to see an update that supports SSHA, since this has been a defacto hashing standard in a few directories for some time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is super important that whatever administrative username you are using needs to have the ability to read the password hash attribute. You can easily test to see if you have the permissions to the password attribute with getXXbyYY.&lt;/P&gt;&lt;PRE&gt;filer9*&amp;gt;&amp;nbsp; getXXbyYY getpwbyname_r gunn
pw_name = gunn
pw_passwd = saltsaltABCDEF
pw_uid = 1000, pw_gid = 1000
pw_gecos = Paul gunn
pw_dir = /home/gunn
pw_shell = /bin/bash
&lt;/PRE&gt;&lt;P&gt;If you don't have the correct permissions, the pw_passwd will always show up as &lt;SPAN style="color: #454545; font-family: Arial, Helvetica, Verdana, sans-serif; background-color: #ffffff;"&gt;pw_passwd = {{******}}&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #454545; font-family: Arial, Helvetica, Verdana, sans-serif; background-color: #ffffff;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 03 Feb 2014 23:11:01 GMT</pubDate>
    <dc:creator>clilescapario</dc:creator>
    <dc:date>2014-02-03T23:11:01Z</dc:date>
    <item>
      <title>NetApp LDAP hashes</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/NetApp-LDAP-hashes/m-p/10192#M2339</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've configured NetApp with LDAP as I found in the TR-3464. I can login into the NetApp through LDAP correctly. The problem starts when a user with the SHA password hash try to login; he doesn't. Only can login if the password is stored with CRYPT hash.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is possible to login with another password hashes? Are there any netapp configuration I forgot?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 05 Jun 2025 06:03:27 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/NetApp-LDAP-hashes/m-p/10192#M2339</guid>
      <dc:creator>SNAKE2000</dc:creator>
      <dc:date>2025-06-05T06:03:27Z</dc:date>
    </item>
    <item>
      <title>Re: NetApp LDAP hashes</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/NetApp-LDAP-hashes/m-p/10196#M2340</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi David,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I never checked into the different hashes, but I can tell you that I encountered the same problem, and my directory uses SSHA1 as the password hash. While not optimal, I worked around it by using ssh keys for each user stored in ldap. In a nutshell the ssh key is the authentication and ldap is used for authorization. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;It would be awesome is someone from netapp could help clarify this.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 17 Jun 2013 18:28:04 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/NetApp-LDAP-hashes/m-p/10196#M2340</guid>
      <dc:creator>clilescapario</dc:creator>
      <dc:date>2013-06-17T18:28:04Z</dc:date>
    </item>
    <item>
      <title>Re: NetApp LDAP hashes</title>
      <link>https://community.netapp.com/t5/ONTAP-Discussions/NetApp-LDAP-hashes/m-p/10200#M2341</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Yes I can confirm that CRYPT will work!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Would love to see an update that supports SSHA, since this has been a defacto hashing standard in a few directories for some time.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What is super important that whatever administrative username you are using needs to have the ability to read the password hash attribute. You can easily test to see if you have the permissions to the password attribute with getXXbyYY.&lt;/P&gt;&lt;PRE&gt;filer9*&amp;gt;&amp;nbsp; getXXbyYY getpwbyname_r gunn
pw_name = gunn
pw_passwd = saltsaltABCDEF
pw_uid = 1000, pw_gid = 1000
pw_gecos = Paul gunn
pw_dir = /home/gunn
pw_shell = /bin/bash
&lt;/PRE&gt;&lt;P&gt;If you don't have the correct permissions, the pw_passwd will always show up as &lt;SPAN style="color: #454545; font-family: Arial, Helvetica, Verdana, sans-serif; background-color: #ffffff;"&gt;pw_passwd = {{******}}&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #454545; font-family: Arial, Helvetica, Verdana, sans-serif; background-color: #ffffff;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;--&lt;/P&gt;&lt;P&gt;Chris&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 03 Feb 2014 23:11:01 GMT</pubDate>
      <guid>https://community.netapp.com/t5/ONTAP-Discussions/NetApp-LDAP-hashes/m-p/10200#M2341</guid>
      <dc:creator>clilescapario</dc:creator>
      <dc:date>2014-02-03T23:11:01Z</dc:date>
    </item>
  </channel>
</rss>

