A copy of #4405
KCM requires the socket peer UID and GID to exactly match the cache owner. It makes no exception for root, even though root can use setuid and setgid to run a process as that user and access the same cache indirectly.
This effectively makes gssproxy unusable with sssd-kcm for my use case and slows down the entire process obtaining a users' credential.
A copy of #4405
KCM requires the socket peer UID and GID to exactly match the cache owner. It makes no exception for root, even though root can use
setuidandsetgidto run a process as that user and access the same cache indirectly.This effectively makes gssproxy unusable with sssd-kcm for my use case and slows down the entire process obtaining a users' credential.