Why do I see different name mapping when using different commands
Applies to
ONTAP 9+
Answer
Name mapping result can vary because different commands different scopes to their data flow.
vserver services access-check name-mapping show- This shows the name-mapping decision the SVM would make when translating an identity based solely on the name mapping configuration:
- Name-mapping rules (
vserver name-mapping) - The direction of mapping (Windows→UNIX or UNIX→Windows)
- The input name format (DOMAIN\user vs user@domain vs plain user)
- No lookup is being performed for the provided user or the expecting mapped user with the configured name services, outside of the mapping itself
- Think of it as: “Given this incoming identity, what would ONTAP map it to?”
- Name-mapping rules (
- This shows the name-mapping decision the SVM would make when translating an identity based solely on the name mapping configuration:
vserver services access-check authentication show-credsorvserver security file-directory show-effective-permissions- This shows the credentials/identity ONTAP actually ended up using for an authentication attempt/session context, which can include:
- The authenticated Windows identity (SID-based) and/or UNIX identity (uid/gid)
- The resolved UNIX user (or Windows user) after identity resolution
- Results influenced by credential caching and the actual protocol path
- Think of it as: “What identity and groups are being used right now for access decisions?”
- This shows the credentials/identity ONTAP actually ended up using for an authentication attempt/session context, which can include:
Additional Information
additionalInformation_text
