Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

idmap_odsam(8) [osx man page]

IDMAP_ODSAM(8)															    IDMAP_ODSAM(8)

idmap_odsam - Open Directory ID mapping backend for winbindd SYNOPSIS
The idmap_odsam plugin is the default backend used by Mac OS X for mapping SIDs and user and group IDs using Open Directory. It implements both the "idmap" and "idmap alloc" APIs. idmap_odsam should always be used in conjunction with the odsam passdb backend. IDMAP OPTIONS
odsam: msglevel = LEVEL LEVEL is the integer log level at which idmap_odsam should emit log messages. The lower LEVEL is, the more verbose the log mes- sages. odsam: traceall = BOOL If this is true, idmap_odsam will emit log messages for all Open Directory calls. If it is false (the default), it will only log errors. IDMAP ALLOC OPTIONS
The idmap_odsam does not allocate any mappings. On Mac OS X, all SID mappings should be made by modifying the appropriate Open Directory record. EXAMPLES
[global] idmap domain = default idmap config default:default = yes idmap config default:backend = odsam idmap alloc backend = odsam passdb backend = odsam odsam: msglevel = 0 # Log at debugging levels odsam: traceall = no # Do not trace Open Directory calls BUGS
Please report bugs to Apple. SEE ALSO
DirectoryService(8), smb.conf(5), winbindd(8) IDMAP_ODSAM(8)

Check Out this Related Man Page

IDMAP_TDB(8)                                                System Administration tools                                               IDMAP_TDB(8)

idmap_tdb - Samba's idmap_tdb Backend for Winbind DESCRIPTION
The idmap_tdb plugin is the default backend used by winbindd for storing SID/uid/gid mapping tables. In contrast to read only backends like idmap_rid, it is an allocating backend: This means that it needs to allocate new user and group IDs in order to create new mappings. The allocator can be provided by the idmap_tdb backend itself or by any other allocating backend like idmap_ldap or idmap_tdb2. This is configured with the parameter idmap alloc backend. Note that in order for this (or any other allocating) backend to function at all, the default backend needs to be writeable. The ranges used for uid and gid allocation are the default ranges configured by "idmap uid" and "idmap gid". Furthermore, since there is only one global allocating backend responsible for all domains using writeable idmap backends, any explicitly configured domain with idmap backend tdb should have the same range as the default range, since it needs to use the global uid / gid allocator. See the example below. IDMAP OPTIONS
range = low - high Defines the available matching uid and gid range for which the backend is authoritative. If the parameter is absent, Winbind fails over to use the "idmap uid" and "idmap gid" options from smb.conf. EXAMPLES
This example shows how tdb is used as a the default idmap backend. It configures the idmap range through the global options for all domains encountered. This same range is used for uid/gid allocation. [global] # "idmap backend = tdb" is redundant here since it is the default idmap backend = tdb idmap uid = 1000000-2000000 idmap gid = 1000000-2000000 This (rather theoretical) example shows how tdb can be used as the allocating backend while ldap is the default backend used to store the mappings. It adds an explicit configuration for some domain DOM1, that uses the tdb idmap backend. Note that the same range as the default uid/gid range is used, since the allocator has to serve both the default backend and the explicitly configured domain DOM1. [global] idmap backend = ldap idmap uid = 1000000-2000000 idmap gid = 1000000-2000000 # use a different uid/gid allocator: idmap alloc backend = tdb idmap config DOM1 : backend = tdb idmap config DOM1 : range = 1000000-2000000 AUTHOR
The original Samba software and related utilities were created by Andrew Tridgell. Samba is now developed by the Samba Team as an Open Source project similar to the way the Linux kernel is developed. Samba 3.5 06/18/2010 IDMAP_TDB(8)
Man Page