Skip to main content
NetApp Knowledge Base

Search

  • Filter results by:
    • View attachments
    Searching in
    About 4 results
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/How_to_encrypt_LDAP_traffic_when_connecting_to_the_Global_Catalog
      Applies to ONTAP 9.x Active Directory Global Catalog LDAP Description In certain scenarios it may be required for the SVM to connect to the Global Catalog server for resolving UNIX credentials ONTAP d...Applies to ONTAP 9.x Active Directory Global Catalog LDAP Description In certain scenarios it may be required for the SVM to connect to the Global Catalog server for resolving UNIX credentials ONTAP does not support encrypted connections over port 3269 If this connection requires encryption to prevent user names and credentials to pass the network in clear text, please follow the steps in the procedure below
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/PTR_with_invalid_IP_causes_secd_conn_auth_failure_notice_or_secd_ldap_noServers_EMERGENCY_errors_in_ONTAP_9
      Errors in the EMS logs: secd.conn.auth.failure:notice or secd.ldap.noServers:EMERGENCY secd: secd.ldap.noServers:EMERGENCY]: None of the LDAP servers configured for Vserver <VServer Name> are currentl...Errors in the EMS logs: secd.conn.auth.failure:notice or secd.ldap.noServers:EMERGENCY secd: secd.ldap.noServers:EMERGENCY]: None of the LDAP servers configured for Vserver <VServer Name> are currently accessible via the network FAILURE: Unable to SASL bind to LDAP server using GSSAPI: Local error Additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Unable to connect to LDAP (Active Directory) service on dc1.demo.netapp.com (Error: Local error)
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/Microsoft_Security_Advisory_ADV190023_impact_on_NetApp_appliance_running_CIFS_NFS_utilizing_Microsoft_Active_Directory_LDAP_servers
      See the following KB for setting up LDAP Signing or Sealing: How to set ONTAP to use LDAP Signing or Sealing for CIFS/NFS Q: LDAP Channel Binding value is supposed to be set to the default value of 1 ...See the following KB for setting up LDAP Signing or Sealing: How to set ONTAP to use LDAP Signing or Sealing for CIFS/NFS Q: LDAP Channel Binding value is supposed to be set to the default value of 1 after patch, do we have to make any changes in ONTAP? As long as the value is kept at 1 and not set to 2, then LDAP channel tokens will not be required and ONTAP will continue to communicate with LDAP.
    • https://kb.netapp.com/on-prem/ontap/da/NAS/NAS-KBs/How_to_set_ONTAP_to_use_LDAP_Signing_or_Sealing_for_CIFS_NFS
      Beginning in ONTAP 9, you can configure signing and sealing to enable LDAP session security on queries to an Active Directory (AD) server. You must configure the CIFS server security settings on the s...Beginning in ONTAP 9, you can configure signing and sealing to enable LDAP session security on queries to an Active Directory (AD) server. You must configure the CIFS server security settings on the storage virtual machine (SVM) to correspond to those on the LDAP server. Sealing encrypts the LDAP payload data to avoid transmitting sensitive information in clear text. An LDAP Security Level option indicates whether the LDAP traffic needs to be signed, signed and sealed, or neither.