Skip to content

Instantly share code, notes, and snippets.

@javigs82

javigs82/iam-comparasion.md

Last active August 20, 2018 15:16
Show Gist options
  • Save javigs82/8e26032504667e5b8b03da5b12c531a5 to your computer and use it in GitHub Desktop.
Save javigs82/8e26032504667e5b8b03da5b12c531a5 to your computer and use it in GitHub Desktop.
Download ZIP
Raw
iam-comparasion.md

IAM Server Comparison

This article aims to explain and show the differences between some important IAM solutions in the OSS market.

WSO2 IAM

Identity and Access management. SSO, oAuth2, OIDC, SAML, IAM. Written in Java. It is the biggest option. As it is a bit old, it is robust, provides lot of features.

  • Pros: Robust, lot of features. ETL for existing user storage. Relies on several RDMS systems. Extensive documentation.
  • Cons: No docker support for OSS. Heavyweight. Un-friendly UI

Hydra

oAuth2 server. SSO, oAuth2 and openId connect server, but NOT identity provider. Written in GO. It is lightweight, modular and it provides a concept called challange to implement login and consent use cases to provide authentication.

  • Pros: Really modular and lightweight (5 MB containers). Docker support
  • Cons: Does not provide identity management. Based on multi tenancy naming convention.

Keycloak

Identity and Access management. SSO, oAuth2, OIDC, SAML, IAM. Written in Java and provided by Red Hat.

  • Pros: Docker. Good Documentation. Relies on several RDMS systems. 2600 git starts and 260 contributors.
  • Cons: Kubernetes.

Gluu

Identity and Access management. SSO, oAuth2, OIDC, SAML, IAM. Written in Java.

  • Pros: New and Modern. Good Documentation.
  • Cons: Docker support is nearly new. Multi tenancy is not really clear. Relies storage on OpenLDAP
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment