Lines Matching full:mapping

8 idmap \- configure and manage the Native Identity Mapping service
88 Mapping service.
91 The Native Identity Mapping service supports the following types of mappings
98 \fBName-based mapping.\fR An administrator maps Windows and UNIX users and
105 \fBEphemeral ID mapping.\fR A UID or GID is dynamically allocated for every SID
112 \fBLocal-SID mapping.\fR A non-ephemeral UID or GID is mapped to an
124 .SS "Mapping Mechanisms"
132 This mapping uses the name-based mappings that are manually set up by the
138 If no name-based mapping is found, the SID is mapped to a dynamically
173 use the mapping information that is stored in user or group objects in the
187 If directory-based name mapping is not configured or if configured but not
188 found, then \fBidmapd\fR(8) will process locally stored name-based mapping
192 \fBidmap\fR supports the mapping of Windows well-known names. A few of these
258 If no name-based mapping is found, a non-ephemeral UID or GID is mapped to an
259 algorithmically generated local SID. The mapping is generated as follows:
274 When mapping a Windows name to a UNIX name, lookup for name-based mapping rules
328 When mapping a UNIX name to a Windows name, lookup for name-based mapping rules
401 Controls support for identity mapping using data stored in a directory service.
403 \fBnone\fR disables directory-based mapping.
405 \fBname\fR enables name-based mapping using the properties described above.
407 \fBidmu\fR enables mapping using Microsoft's Identity Management for UNIX
409 ID for each Windows user, mapping the Windows identity to the corresponding
436 The \fBusermap.cfg\fR rule-mapping format is as follows:
456 \fB==\fR means a bidirectional mapping, which is the default.
462 \fB=>\fR or \fB<=\fR means a unidirectional mapping.
470 The \fBsmbusers\fR rule-mapping format is as follows:
501 By default, if no mapping entries are in the \fBsmbusers\fR file, Samba maps a
503 set up the same mapping as Samba does, use the following \fBidmap\fR command:
628 (\fBwinuser\fR, \fBwingroup\fR) that can be used for name-based mapping rules.
648 \fIname\fR, which uses the default mapping domain
650 If \fIname\fR is the empty string (\fB""\fR), mapping is inhibited. Note that a
659 If \fIname\fR uses the wildcard on both sides of the mapping rule, the name is
676 specifies the mapping type that should be shown. For example, if
706 Adds a name-based mapping rule. By default, the name mapping is bidirectional.
707 If the \fB-d\fR option is used, a unidirectional mapping is created from
716 opposite directions are equivalent to one bidirectional mapping.
741 Exports name-based mapping rules to standard output in the specified
753 Get the directory-based name mapping information from the AD or native LDAP
774 Imports name-based mapping rules from standard input by using the specified
776 file. The \fB-F\fR option flushes existing name-based mapping rules before
793 Lists all name-based mapping rules. Each rule appears in its \fBidmap add\fR
804 Removes any name-based mapping rule that involves the specified name.
821 Removes all name-based mapping rules.
833 Removes name-based mapping rules between \fIname1\fR and \fIname2\fR. If the
851 Sets name mapping information in the AD or native LDAP user or group object.
902 maps to. If the optional \fItarget-type\fR is omitted, the non-diagonal mapping
906 already. The \fB-c\fR option forces the evaluation of name-based mapping
909 The \fB-v\fR option shows how the mapping was generated and also whether the
910 mapping was just generated or was retrieved from the cache.
921 Unsets directory-based name mapping information from the AD or native LDAP user
928 \fBExample 1 \fRUsing a Wildcard on Both Sides of a Name-Based Mapping Rule
934 exist, an ephemeral ID mapping is used.
945 \fBExample 2 \fRUsing a Wildcard on One Side of a Name-Based Mapping Rule
950 unidirectional mapping from \fB*@example.com\fR users to the \fBguest\fR user.
961 \fBExample 3 \fRAdding a Bidirectional Name-Based Mapping Rule
977 This command shows how to remove the mapping added by the previous command:
988 \fBExample 4 \fRShowing a UID-to-SID Mapping
1080 \fBExample 7 \fRListing Name-Based Mapping Rules
1083 The following command shows how to list the name-based mapping rules:
1096 \fBExample 8 \fRImporting Name-Based Mapping Rules From the \fBusermap.cfg\fR
1100 The \fBusermap.cfg\fR file can be used to configure name-based mapping rules.
1101 The following \fBusermap.cfg\fR file shows mapping rules that map Windows user
1157 \fBExample 9 \fRUsing Name-Based and Ephemeral ID Mapping With Identity
1158 Function Mapping and Exceptions
1183 \fBExample 10 \fRAdding Directory-based Name Mapping to AD User Object
1198 \fBExample 11 \fRAdding Directory-based Name Mapping to Native LDAP User Object
1214 \fBExample 12 \fRRemoving Directory-based Name Mapping from AD User Object