Difference between revisions of "Identity Mapping Back Ends"
From SambaWiki
Mmuehlfeld (talk | contribs) (Moved note about testparm bug out of the warning box. It's nothing we need to warn about. Therefore it's better not to put it in a warning admonition. Additionally, the warning is about something different and just appending it it was not clearly visible) |
m (/* Moved 'testparm' note into an info box, so it is more visible, removed 'incorrect' because it is technically correct, the line is shown if you run 'testparm -v', re-added that it can be ignored, there is no point to the note otherwise!) |
||
| Line 24: | Line 24: | ||
}} |
}} |
||
| + | {{Imbox |
||
| ⚫ | |||
| + | | type = note |
||
| − | |||
| ⚫ | |||
| + | }} |
||
Revision as of 12:31, 19 March 2017
Supported ID Mapping Back Ends
Samba provides the following ID mapping back ends:
- idmap config ad (RFC2307)
- idmap config rid
- idmap config autorid
- idmap config hash
- idmap config ldap
- idmap config nss
Using ID Mapping Back Ends on a Samba AD DC
For setting up Winbindd a Samba Active Directory (AD) domain controller (DC), see Configuring Winbindd on a Samba AD DC.
 | ID mapping back ends are not supported in the smb.conf file on a Samba AD DC. For details, see Failure to Access Shares on Domain Controllers If idmap config Parameters Set in the smb.conf File. |
 | On a Samba 4.6.x AD DC, the testparm utility displays ERROR: Invalid idmap range for domain *! You can safely ignore this, For details, see Bug #12629. |