Keycloak vs Dex

Keycloak and Dex both are OIDC provider and frequently adopted in Kubernetes. They are sponsored by RedHat as well.

I had a chance to deploy and use them in our Kubernetes environment, and came up the list of comparison:

Keycloak supports everything Dex can provide:

Keycloak also has more features:

Dex is an OIDC provider. It’s simple and easy to setup. Keycloak is literally an Identity and Access Management service ,It requires Database (PostgreSQL, MySQL, MariaDB, and H2) to store user and group data so you will have to manage own database.

It’s all depends on your requirements and infrastructure:

If you already have existing Identity Provider (AD, SAML, Github..etc) and just need an OIDC interface to bridge applications with a centralized service. Dex is your choice.

If you need custom claim from OIDC provider and also looking for replace existing Identity provider. And you expect more programatic automation with Identity provider. Keycloak definitely can fulfill the requirement and with REST API support.

Hope this article gave you more ideas for both wonderful OIDC providers in Kubernetes.

Related posts:

Inviting Leese Wright | Anjali Samaraweera | Sneha Devaraj | Meenal Gupta | Suman Sandhu | Crystalclearcandace | HerPrivateLife | ScienceDuuude | Sruthi Korlakunta| Aaron Kemp | if you’re up to it…

Are you an Outlook user looking to move Outlook emails from OST to MSG files? If the answer to that question is yes, this blog may be the ideal setting for you. Here, we’ll give you a way to convert…

Suatu malam di sudut kota yang gelap, lembab yang memuakkan karena kemarau meriang disiram hujan, pria itu, dengan setelan bajunya yang menutupi 90 persen tubuhnya menunggu seseorang yang sedang…