Sun Microsystems, Inc.  Oracle System Handbook - ISO 7.0 May 2018 Internal/Partner Edition
   Home | Current Systems | Former STK Products | EOL Systems | Components | General Info | Search | Feedback

Asset ID: 1-72-1542555.1
Update Date:2016-02-05
Keywords:

Solution Type  Problem Resolution Sure

Solution  1542555.1 :   Oracle ZFS Storage Appliance: Rule-based Identity Mapping Fails  


Related Items
  • Sun ZFS Storage 7420
  •  
  • Sun Storage 7110 Unified Storage System
  •  
  • Oracle ZFS Storage ZS3-2
  •  
  • Sun Storage 7210 Unified Storage System
  •  
  • Oracle ZFS Storage ZS4-4
  •  
  • Sun Storage 7410 Unified Storage System
  •  
  • Sun Storage 7310 Unified Storage System
  •  
  • Sun ZFS Storage 7120
  •  
  • Oracle ZFS Storage ZS3-4
  •  
  • Sun ZFS Storage 7320
  •  
  • Oracle ZFS Storage Appliance Racked System ZS4-4
  •  
  • Oracle ZFS Storage ZS3-BA
  •  
Related Categories
  • PLA-Support>Sun Systems>DISK>ZFS Storage>SN-DK: 7xxx NAS
  •  




In this Document
Symptoms
Cause
Solution
References


Created from <SR 3-6560572637>

Applies to:

Sun ZFS Storage 7320 - Version All Versions and later
Sun ZFS Storage 7120 - Version All Versions and later
Sun Storage 7110 Unified Storage System - Version All Versions and later
Sun Storage 7210 Unified Storage System - Version All Versions and later
Sun Storage 7310 Unified Storage System - Version All Versions and later
7000 Appliance OS (Fishworks)

Symptoms

 Identity mapping is configured correctly, but rule matching fails.

This results in an ephemeral ID being assigned despite an exact match for the username rule.

This can be verified in the BUI page for the Identity Mapping service, by entering a user name which has an active mapping rule, and observing the mapped UID.

Cause

There is currently a defect in the software that causes the domain name portion of the mapping rule to be compared case sensitively.

So, for example, if a mapping rule was created for a user in "oracle.com", and the actual name of the Windows Domain is "Oracle.Com", the matching rule will fail.

Note: Windows Domain names are considered to be case insensitive, but case preserving.

 

Solution

As a workaround, until this defect is addressed in a future software release, you must determine the exact case of the Windows Domain name, and use that "case-correct" domain name in the mapping rule.

To definitively determine the Windows Domain name, open the "Domains and Trusts" applet from within Administrative Tools on a Domain Controller. The Domain name will be displayed to the top left.

 

This is Bug:15485181, once this issue is resolved, we won't need this workaround.

 

References

<BUG:15485181> - SUNBT6710657 DOMAINNAME CASE ISSUES IN EPHEMERAL ID MAPPING

Attachments
This solution has no attachment
  Copyright © 2018 Oracle, Inc.  All rights reserved.
 Feedback