Considering deprecating Keycloak Spring Boot and Security adapters

[Stian Thorgersen]

With Spring Security 5 there is good support for OpenID Connect and OAuth 2 directly in Spring. 

Due to this we are considering deprecating the Keycloak specific Spring Boot and Security adapters.

[Manfred Duchrow]

To be honest, I have not yet looked at the capabilities of Spring Security 5, but I doubt that these generic OIDC/OAuth2 adapters
cover important features like transferring roles from access token into Authentication / GrantedAuthority objects or support for
not yet standardized logout (k_logout). Another missing feature would perhaps be parameter forwarding (e.g. kc_idp_hint).

IMO before dropping Keycloak Spring Boot and Security adapters, somebody should at least verify if it's possible ti extend
these generic Spring Security OIDC/OAuth2 adapters to support the (Keycloak specific) capabilities mentioned above.

[Pedro Igor Craveiro e Silva]

I think it is worthy to mention that this same strategy we are using to Quarkus, which should become our generic adapter for Quarkus-based apps. See 

On Thu, Mar 5, 2020 at 10:54 AM Stian Thorgersen <stho...@redhat.com> wrote:

With Spring Security 5 there is good support for OpenID Connect and OAuth 2 directly in Spring. 

Due to this we are considering deprecating the Keycloak specific Spring Boot and Security adapters.

--
You received this message because you are subscribed to the Google Groups "Keycloak Dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to keycloak-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/keycloak-dev/CAJgngAdytFw8wAeid-PeQe9iieVEnzRRBwg1%2B3zNkOYFM1DfOA%40mail.gmail.com.

[Blazej Adamczyk]

Replying really late to this thread but I've just read the deprecation info in latest release notes..

Pedro, Stian can you please shed some light on the plans of spring adapter deprecation? As you stated oidc and oauth2 is indeed covered by spring but what with authorization, policy enforcement and uma-2 support?

I'm worried becuase we are using these adapters in our spring apps and frequently with policy enforcement.

Thanks in advance for any response!

[Robert Schuh]

We are using the uma 2 features of it heavily and having the whole adapter deprecated would mean having to rebuild it…?
Maybe its possible to still maintain these features (authz, policies, uma2) in a trimmed down version that works on top of spring oidc support? 

[Błażej Adamczyk]

Dear Authors, Stian, Pedro,

Can you please shed some more light on your plans regarding springboot
in the context of authz/uma2 support?

Thanks!

--
Kind regards,
Błażej Adamczyk, Ph.D.
Silesian University of Technology
Institute of Computer Science
Akademicka 16
44-100 Gliwice, Poland
Phone: +48 601 180 169
PGP: 0xCBAF608AE20B06F2C172A853B70E6F797423F7B7 (pgp.mit.edu)

-------- Wiadomość oryginalna ----------
Od: 'Robert Schuh' via Keycloak Dev <keyclo...@googlegroups.com>
Odpowiedź do: Robert Schuh <rv.s...@googlemail.com>
Do: Keycloak Dev <keyclo...@googlegroups.com>
Temat: Re: [keycloak-dev] Considering deprecating Keycloak Spring Boot
and Security adapters
Data: Sat, 11 Dec 2021 13:01:59 -0800 (PST)

[Stian Thorgersen]

We will share more information as soon as we have it available. Rest assured we won't remove any adapters until we have found acceptable alternative solutions.