sin/samba-mirror
1
0
Fork 0
mirror of https://github.com/samba-team/samba.git synced 2025-08-26 01:49:31 +03:00
Code Activity

docs-xml: add "winbind use krb5 enterprise principals" option

Browse Source 
BUG: https://bugzilla.samba.org/show_bug.cgi?id=14124

Signed-off-by: Stefan Metzmacher <metze@samba.org>
Reviewed-by: Guenther Deschner <gd@samba.org>
This commit is contained in:
Stefan Metzmacher
2019-09-11 16:44:43 +02:00
committed by Günther Deschner
parent 3bdf023956
commit 9520652399
1 changed files with 34 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

34
docs-xml/smbdotconf/winbind/winbindusekrb5enterpriseprincipals.xml Normal file
View File

@ -0,0 +1,34 @@
<samba:parameter name="winbind use krb5 enterprise principals"
context="G"
type="boolean"
xmlns:samba="http://www.samba.org/samba/DTD/samba-doc">
<description>
<para>winbindd is able to get kerberos tickets for
pam_winbind with krb5_auth or wbinfo -K/--krb5auth=.
</para>
<para>winbindd (at least on a domain member) is never be able
to have a complete picture of the trust topology (which is managed by the DCs).
There might be uPNSuffixes and msDS-SPNSuffixes values,
which don't belong to any AD domain at all.
</para>
<para>With <smbconfoption name="winbind scan trusted domains">no</smbconfoption>
winbindd don't even get an incomplete picture of the topology.
</para>
<para>It is not really required to know about the trust topology.
We can just rely on the [K]DCs of our primary domain (e.g. PRIMARY.A.EXAMPLE.COM)
and use enterprise principals e.g. upnfromB@B.EXAMPLE.COM@PRIMARY.A.EXAMPLE.COM
and follow the WRONG_REALM referrals in order to find the correct DC.
The final principal might be userfromB@INTERNALB.EXAMPLE.PRIVATE.
</para>
<para>With <smbconfoption name="winbind use krb5 enterprise principals">yes</smbconfoption>
winbindd enterprise principals will be used.
</para>
</description>
<value type="default">no</value>
<value type="example">yes</value>
</samba:parameter>