Bump Keycloak version to 22.0.0

[pedroigor]

No description provided.

[sberyozkin]

Great stuff thanks @pedroigor

[sberyozkin]

Checking locally

[sberyozkin]

CodeFlowTest.testAccessAndRefreshTokenInjectionWithoutIndexHtmlAndListenerMultiTab is failing, I'll have a look

[sberyozkin]

@pedroigor Many thanks for the PR, minor issue in the test related to the multi-tab setup which I fixed, I'll check it outside the test setup - but as far as Quarkus is concerned it can't affect how KC responds in such cases so we can chat about it afterwards and see what/if might need to be tweaked further

[sberyozkin]

@pedroigor For Keycloak 20, 21, 22 I get now 401 as well in the browser, with Cookie not found. Please make sure cookies are enabled in your browser., While test gets an expected You are already logged in. It feels like it is the browser related configuration which influences it. I'm pretty sure that specifically Keycloak users confirmed multi-tab was working fine for them and I did try it in the quickstart before writing a test - as I needed to know what Keycloak would return in the first tab to verify it in the test.

But in any case - this is definitely not something Quarkus can influence, it is between the browser and Keycloak, so I'm not worried. If I see users documenting how this should be worked around then I can add some advice to our docs...

Thanks

[quarkus-bot]

Failing Jobs - Building 152f93b

Status	Name	Step	Failures	Logs	Raw logs
⌛	JVM Tests - JDK 11	Build	⚠️ Check →	Logs	Raw logs
✔️	JVM Tests - JDK 17
✔️	JVM Tests - JDK 19
✔️	Maven Tests - JDK 11
⌛	Maven Tests - JDK 11 Windows	Build	⚠️ Check →	Logs	Raw logs

[sberyozkin]

Tests look ok. Keycloak authorization is the only integration point. For dev services changing a KC image name is easy

[gsmet]

Is it something that we want in 3.2?

[maxandersen]

So 22.0 is what is supposed tonight be used in 3.2 - but there is an open question about forward and backwards compatibility of the client that the Keycloak team is going to investigate next week.

[sberyozkin]

Added a breaking-change label due to #35572 - even though it is not a keycloak-authorization specific breaking change

[sberyozkin]

@maxandersen @gsmet See #35572, for it to be backported to 3.2, keycloak-adapter-core dependency which is no longer needed after the update to KC 22.0.1, would have to be re-introduced as users may be depending on some code from this dependency