Skip to main content
NetApp Knowledge Base

Why does ONTAP name-map for both UNIX and AD for S3 users?

  1. Last updated
  2. Save as PDF
Views:
203
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • ONTAP 9
  • ONTAP S3 (S3)
  • Name-mapping

Answer

  • ONTAP attempts to name-map for both UNIX and AD when ONTAP authenticates any S3 user.
    • There is no way to prevent this function.

Example:

secd.nfsAuth.noCifsCred:vserver (VS1)
NFS authorization cannot retrieve CIFS credentials. 
Error: Get user credentials procedure failed 
[ 4] S3 user 'user1' mapped to UNIX user 'pcuser' 
[ 4] S3 user 'user1' mapped to Windows user 'DOMAIN\user1' 
[ 4] Using cached 'DOMAIN\user1' SID mapping. 
[ 8] Successfully connected to ip 192.168.0.1, port 88 using TCP 
[ 53] Could not get credentials via S4U2Self based on full Windows user name 'user1@DOMAIN.LOCAL'. Continuing to LDAP. 
[ 55] Successfully connected to ip 192.168.0.1, port 389 using TCP [ 97] Using a cached connection to dc1.domain.local

 

Additional Information

N/A
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.