Flushing Mappings from the Cache (BUI)
■
If you selected Windows, type the Windows domain and name of the user.
■
If you selected UNIX, choose either User or Group for the type, and type the
entity name.
4.
Click SHOW MAPPING.
The identity user or group properties are displayed. The mapping source and backend origin are
also displayed:
Source
■
New mapping - The mapping was newly created and was neither retrieved from the cache
nor predefined.
■
Cached mapping - The mapping was retrieved from the cache, where mappings are stored
for 10 minutes after they are requested.
■
Hard coded mapping - The mapping is predefined and fixed on the appliance. These
mappings were created for default UNIX and Windows identities.
■
Algorithmic mapping - A non-ephemeral UNIX UID or GID could not be mapped by
name, so it was mapped to an algorithmically generated SID.
Backend
■
AD Directory - This is a directory-based mapping that was created using annotations in the
Active Directory.
■
Native LDAP Directory - This is a directory-based mapping that was created using
annotations in the LDAP directory.
■
IDMU - The mapping was created using the Windows feature Identity Management for
UNIX.
■
Name rule - The mapping was created using a name rule.
■
Ephemeral - Since there was no equivalent identity at the time the mapping was created,
the system created a temporary one using an ephemeral UID or GID.
■
Local SID - A non-ephemeral UNIX UID or GID could not be mapped by name, so it was
mapped to an algorithmically generated local SID.
■
Well-known mapping - The mapping uses a "well-known SID." These Windows SIDs
identify generic users or generic groups. Their values remain constant across all operating
systems.
Flushing Mappings from the Cache (BUI)
Use the following procedure to flush, or expire, all mappings from the cache.
306 Oracle ZFS Storage Appliance Administration Guide, Release OS8.6.x • September 2016
To Next Page
Loading...
Need help?
General
