s4:kdc: Add asserted identity SID to identify whether S4U2Self has occurred
commit9ad03f51a34359c9b0d513dd8c3c17b635469c8f
authorAndreas Schneider <asn@samba.org>
Mon, 11 Oct 2021 12:47:25 +0000 (11 14:47 +0200)
committerAndreas Schneider <asn@cryptomilk.org>
Wed, 13 Apr 2022 13:54:27 +0000 (13 13:54 +0000)
tree7f6d42ecae2e5ef1a829b143803a4a485d5ff0c0
parent9b03e31fba7aa726f3c481f18f9e9e5b4c96c381
s4:kdc: Add asserted identity SID to identify whether S4U2Self has occurred

Because the KDC does not limit protocol transition (S4U2Self), two new
well-known SIDs are available to give this control to the resource
administrator. These SIDs identify whether protocol transition (S4U2Self) has
occurred, and can be used with standard access control lists to grant or limit
access as needed.

See
https://docs.microsoft.com/en-us/windows-server/security/kerberos/kerberos-constrained-delegation-overview

Pair-Programmed-With: Stefan Metzmacher <metze@samba.org>

Signed-off-by: Andreas Schneider <asn@samba.org>
Signed-off-by: Stefan Metzmacher <metze@samba.org>
Autobuild-User(master): Andreas Schneider <asn@cryptomilk.org>
Autobuild-Date(master): Wed Apr 13 13:54:27 UTC 2022 on sn-devel-184
selftest/knownfail.d/asserted_identity [deleted file]
selftest/knownfail.d/rpc.pac [deleted file]
selftest/knownfail.d/samba4.tokengroups [deleted file]
source4/kdc/mit_samba.c
source4/kdc/pac-glue.c
source4/kdc/pac-glue.h
source4/kdc/wdc-samba4.c