When S4U2Self is requested by a service from IPA realm utilizing enterprise principal, impersonated user might actually come from a trusted forest. In such case the target service will not receive PAC of the user in the current implementation of FreeIPA KDB driver.
PAC record in the S4U2Self can be used by the service to obtain most up to date information about user's group membership as seen by the client's realm KDC. There are applications which utilize this: Microsoft SQL Server is one of those, but https://github.com/SSSD/sssd/issues/5043 suggests we want it to be supported for SSSD as well.
The purpose of this ticket is to track initial S4U2Self over cross-realm support for enterprise princpials. While there are limits of what could be supported in MIT Kerberos before 1.18, we probably can make the path of 'service in IPA realm, client in AD forest' supported.
Metadata Update from @abbra: - Issue assigned to abbra - Issue set to the milestone: FreeIPA 4.8
PR: https://github.com/freeipa/freeipa/pull/4677
master:
ipa-4-8:
Metadata Update from @abbra: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.