Difference between revisions of "Identity Mapping Back Ends"
From SambaWiki
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!) |
m (broken link fixed) |
||
| Line 21: | Line 21: | ||
{{Imbox |
{{Imbox |
||
| type = warning |
| type = warning |
||
| − | | text = ID mapping back ends are not supported in the <code>smb.conf</code> file on a Samba AD DC. For details, see [[ |
+ | | text = ID mapping back ends are not supported in the <code>smb.conf</code> file on a Samba AD DC. For details, see [[Updating_Samba#Failure_To_Access_Shares_on_Domain_Controllers_If_idmap_config_Parameters_Set_in_the_smb.conf_File|Failure to Access Shares on Domain Controllers If idmap config Parameters Set in the smb.conf File]]. |
}} |
}} |
||
Revision as of 13:11, 27 April 2018
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. |