Skip to main content
NetApp Knowledge Base

The SASL bind to UNIX LDAP server fails with Local error

Views:
1,263
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • FreeIPA LDAP server
  • LDAP SASL bind

Issue

  • Using FreeIPA as an external LDAP server, the storage fails SASL bind to the LDAP server with the following SecD log

Tue Aug 03 2021 10:48:04 +02:00 [kern_secd:info:91312] [ 0] Resolved LDAP servers: 10.10.10.10. Vserver: 6

Tue Aug 03 2021 10:48:04 +02:00 [kern_secd:info:91312] [ 42] Successfully connected to ip 10.10.10.10, port 389 using TCP

Tue Aug 03 2021 10:48:04 +02:00 [kern_secd:info:91312] [ 44] Entry for host-address: 10.10.10.10 not found in the current source: FILES. Ignoring and trying next available source

Tue Aug 03 2021 10:48:04 +02:00 [kern_secd:info:91312] **[ 69] FAILURE: Unable to SASL bind to LDAP server using GSSAPI: Local error

Tue Aug 03 2021 10:48:04 +02:00 [kern_secd:info:91312] [ 69] Additional info: SASL(-1): generic failure: GSSAPI Error: Unspecified GSS failure. Minor code may provide more information (Server ldap/dc01.ntap.local@NTAP.LOCAL not found in Kerberos database)

  • Check DNS to ensure that all LDAP servers that ONTAP may connect to have a single, correct PTR record

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.