keycloak
Open Source Identity and Access Management For Modern Applications and Services
Keycloak: identity management without the plumbing
Open source identity and access management for modern applications, aimed at developers who would rather add authentication than store and verify users themselves.
What it does
Keycloak is open source identity and access management for modern applications and services. The README makes the promise concrete: developers can add authentication to applications and secure services with minimum effort, and they never have to deal with storing or authenticating users themselves. The phrase modern applications and services recurs through the document and sets the tone for everything that follows. Java is the primary language, the license is Apache-2.0, and the homepage is keycloak.org.
The capability list
The feature list runs through user federation, strong authentication, user management, and fine grained authorization, with a trailing and more. Read together, those add up to a full identity platform rather than a login widget you drop into one app. That scope is the reason the support and contribution sections exist the way they do.
Help, development, and reporting
A user mailing list handles help and general questions. A Slack workspace is where design and development discussions happen. Security vulnerabilities follow documented reporting instructions, and defects should be opened as issues with a good summary, description, and reproduction steps. The README keeps these channels distinct, which is useful when you need to know where your message belongs.
Audience and framing
The whole document is pitched at developers building modern applications and services. Beyond the feature list, the README is mostly support infrastructure: mailing list, Slack workspace, issue reporting guidance, and a homepage at keycloak.org. The channels are kept deliberately separate, so a question lands where it belongs the first time.
Community notes