91–100 of 124 posts
I have created OpenAPI (Swagger) schemas for Keycloak's admin rest API. https://github.com/ccouzens/keycloak-openapi/tree/master/key... Hopefully these are useful to other people. See the parent directory for the tooling I wrote to generate them from Keycloak's HTML documentation.
It seems like a lot of people have seen the light now and are evaluating Keycloak even though it has been around for so long. did something happen recently that I'm missing out on?
Earlier quoted context omitted.
Keycloak is an authentication portal that sits in front of other applications thereby freeing those applications from the burden of implementing login forms and secure password storage.
"that sits in front of " does that denote that miminal refactor / re-architecture is needed for a rest based application, trying to get an idea of how easy it is to start using keycloak?
Whenever you want someone authenticated you redirect the user's browser to Keycloak. Keycloak will redirect the user's browser back to you once authentication has been completed. In the best case scenario you will find a library that integrates with your choice of web framework, provide configuration (i.e. the URL to Keycloak), and the library will do all the heavy lifting for you.
I found Keycloak as a product relatively easy to get started with. But I still don't think I fully understand the authentication landscape with its' many alternatives and their many security implications.
Earlier quoted context omitted.
Setting up OpenLDAP or 389ds and integrating Keycloak with it is hardly rocket science - no need to reinvent the wheel.
Setting it up with FreeIPA (which contains 389ds) is a matter of filling up a single form in Keycloak admin. That includes SPNEGO (passwordless auth in browser) for those, who are enrolled into domain or have Kerberos tickets.
One feature that stands out is for me the social login integration: a few clicks and they just work. Between the downsides, I have to mention the fact that since it's an external tool you need to take care of monitoring, uptimes and upgrades separately from your application.
Recently I started a little side project to create some themes for Keycloak, the original look and feel is very "enterprise" and I thought about creating more modern alternatives that you can install and customize in minutes. I don't know if it's interesting for someone, but in case you are interested you can follow the progress at https://keycloakthemes.com and maybe subscribe to the newsletter to be notified when I release the first theme.
It seems like a lot of people have seen the light now and are evaluating Keycloak even though it has been around for so long. did something happen recently that I'm missing out on?
Microservices and api management gets more popular. (and the need for jwt/oauth) since redhat is generally trusted. It is basically the only option if you want to use it.
RedHat has some nice software designers - design for extensibility is visible in every product they create. And adhering to standards like the Java EE web framework instead of going the NIH style of Spring. After 2 or 3 major releases the Spring APIs start showing signs of leaky abstractions or outright confusing mess.
Earlier quoted context omitted.
Setting it up with FreeIPA (which contains 389ds) is a matter of filling up a single form in Keycloak admin. That includes SPNEGO (passwordless auth in browser) for those, who are enrolled into domain or have Kerberos tickets.
FreeIPA has it's own set of problems. One being basically unrunnable in containers because of weird systemd stuff
It has nothing to do with systemd, despite what systemd-phobes think.
Keycloak is a great piece of engineering. It's a robust IAM, fully-featured, easy to deploy and integrate with. My opinion is that people should rely on battle-tested 3rd party solution like Keycloak for their authentication and authorization needs. We run it in production on GCP and it integrates nicely with the Clojure ecosystem (both on the frontend with a SPA and on the backend dealing with REST API security). Sh…
Keycloak is a great piece of engineering. It's a robust IAM, fully-featured, easy to deploy and integrate with. My opinion is that people should rely on battle-tested 3rd party solution like Keycloak for their authentication and authorization needs. We run it in production on GCP and it integrates nicely with the Clojure ecosystem (both on the frontend with a SPA and on the backend dealing with REST API security). Sh…
Good to hear that a Clojure wrapper is there. I've been thinking about Keycloak, but I was worried that the login or credentials management UI would be outside of my app (and different). But perhaps there is a way to integrate with it while keeping the UI in-app?