Hello everyone.
On our platform we use Keycloak to manage user logins.
We’ve worked with GeoServer 2.22.3 and 2.28.3, and the OIDC extension has worked really good.
We recently installed GeoServer 3.0-RC to test the new version, and we’re unable to get the OIDC extension to work (we’ve tested both the 3.0-RC and 3.0-SNAPSHOT extensions).
There’s no error message on console, but the Keycloak login icon simply doesn’t appear at the top. Checking the Keycloak logs, we also found no trace of it.
So, I’d like to ask if anyone has tested this extension on 3.0-RC and gotten it working, and if so, what the trick was 
We know the extension is still marked as pending, but we’d like to know if anyone has had it working. I seem to recall reading that it’s planned to be included as an official module in version 3.0.1, so I don’t know if it’s just a matter of waiting and that’s it.
Cheers.
Hello,
yes, that’s confirmed. The OIDC login button is not yet aligned to the new UI refactoring. I’ll work on that. Thanks for your feedback.
Thanks to you, Alessio.
We’ll keep an eye out for updates.
Cheers.
Turns out the filter was already working but a wrong bean registration required a GeoServer restart in order to show the buttons.
Anyway, I took the occasion to fix this and some more other issues and improvements.
PR here fix(oidc): expose dynamic login buttons via ExtensionProvider and OIDC multi button login by afabiani · Pull Request #9499 · geoserver/geoserver · GitHub
Morning, Alessio.
Thanks for the tip.
We tried restarting GeoServer with the OIDC extension + Keycloak configured, but the icon it still doesn’t appear on the front-end.
We will be monitoring the progress of the fix.
Thanks!
PR merged, build the plugin again and try to reconfigure it. Notice that the redirect_uri will be different.
Let me know.
Afternoon.
We have tried the last version (May 14) of the 3.0.0-SNAPSHOT OIDC plugin, and is already working.
It logs in correctly against our Keycloak, so it works perfectly.
Thank you, Alessio!
