diff options
Diffstat (limited to 'docs/smbdotconf/security/usernamemap.xml')
| -rw-r--r-- | docs/smbdotconf/security/usernamemap.xml | 7 |
1 files changed, 4 insertions, 3 deletions
diff --git a/docs/smbdotconf/security/usernamemap.xml b/docs/smbdotconf/security/usernamemap.xml index 59c0cdde7c..54179690be 100644 --- a/docs/smbdotconf/security/usernamemap.xml +++ b/docs/smbdotconf/security/usernamemap.xml @@ -15,7 +15,7 @@ Please note that for user or share mode security, the username map is applied prior to validating the user credentials. Domain member servers (domain or ads) apply the username map after the user has been successfully authenticated by the domain controller and require fully qualified enties in the map table (e.g. - biddle = DOMAIN\foo). + biddle = <literal>DOMAIN\foo</literal>). </para> <para> @@ -96,7 +96,8 @@ guest = * </para> <para> - Samba versions prior to 3.0.8 would only support reading the fully qualified username (e.g.: DOMAIN\user) from + Samba versions prior to 3.0.8 would only support reading the fully qualified username + (e.g.: <literal>DOMAIN\user</literal>) from the username map when performing a kerberos login from a client. However, when looking up a map entry for a user authenticated by NTLM[SSP], only the login name would be used for matches. This resulted in inconsistent behavior sometimes even on the same server. @@ -113,7 +114,7 @@ guest = * <para> When relying upon a external domain controller for validating authentication requests, smbd will apply the username map - to the fully qualified username (i.e. DOMAIN\user) only after the user has been successfully authenticated. + to the fully qualified username (i.e. <literal>DOMAIN\user</literal>) only after the user has been successfully authenticated. </para> <para> |