On 31 Aug 2026, at 09:42, Alexander Bokovoy via FreeIPA-users <freeipa-users@lists.fedorahosted.org> wrote:
On Fri, 28 Aug 2026, Francis Augusto Medeiros-Logeay via FreeIPA-users wrote:Hi,I developed a Keycloak extension (Keycloak PSSO extension) so that users of managed macOS machines get SSO.The framework used - Platform Single Sign-on - also allows returning kerberos tickets.But I'm not sure how Keycloak could programmatically return kerberos tickets for a user without the password. Some of the pPlatform SSO flows do not involve using passwords.
Standard way of achieving this is to let a service to perform Kerberos
protocol transition (S4U operations). S4U2Self is allowed to any
service, S4U2Proxy is privileged. This is what IPA API is using already.The idea I had first was to use my extension with some keytab with permissions to request kerberos tickets on behalf of other users.But has FreeIPA support for OAuth2 tokens, so that I could simply exchange an OAuth2 token to a kerberos tickets?This would be easier since I already control token issuing on the keycloak side.
You can create your own OAuth2 service with a Kerberos service keytab
and then handle it there. The service will have to be explicitly allowed
to perform operations on behalf of users towards IPA services.
I have integration like that done for Ahdapa, see the design and the code in the
work in progress modrnizer branch here:
https://github.com/abbra/freeipa/blob/modrnizer/doc/designs/webui-oauth2-login.md
and Ahdapa side endpoint documentation here:
https://ahdapa.dev/doc/api/internal.html#credential-exchange-oidc-to-kerberos
Ahdapa is a next generation integrated OAuth2 IdP for FreeIPA,
https://forge.fedoraproject.org/freeipa/ahdapa
Note that the code in modrnizer branch is building on top of gssproxy
integration for existing IPA HTTP service, so we cannot use the issued
ccache outside IPA server itself: the credentials in the ccache are
encrypted by gssproxy and can only be decrypted by the same gssproxy
session. However, Ahdapa can be set up as a separate IdP endpoint on
enrolled IPA client and joined the same IPA topology. If that is done in
a way that doesn't use gssproxy, then the ccache produced by that
instance's OBO endpoint would be usable beyond that service point.
If you want to try it, use COPR abbra/modrnizer for experiments.
--
/ Alexander Bokovoy
Sr. Principal Software Engineer
Security / Identity Management Engineering
Red Hat Limited, Finland
--
_______________________________________________
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-leave@lists.fedorahosted.org
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedorahosted.org/archives/list/freeipa-users@lists.fedorahosted.org
Do not reply to spam, report it: https://forge.fedoraproject.org/infra/tickets/issues/new