Skip to content

Users, Groups & Credentials

Keycloak keeps a clear separation between who someone is (their identity), how they prove it (credentials), and what they are allowed to do (roles and permissions). This module focuses on the identity side of that equation.

By the end of this module you will know how to create and manage users, organise them into groups, assign and reset credentials, and drive users through required actions — all inside the Keycloak admin console and via the Admin REST API.

OrderLessonWhat you will learn
1UsersCreate users, manage attributes, enable or disable accounts, verify email
2GroupsCreate group hierarchies, add users to groups, inherit roles through group membership
3CredentialsSet passwords, reset credentials, configure OTP, understand credential priority
4Required ActionsAssign built-in actions (verify email, update password, configure OTP), create custom actions
5User FederationConnect an LDAP or Active Directory server, configure mappers, sync users on demand

A user is a record stored inside a realm. The realm is the boundary — users in realm my-app cannot log in to realm other-app unless their account exists there too.

Groups let you bundle users so you can manage role assignments, attributes, and required actions in one place rather than per-user. Groups can be nested into a hierarchy.

Credentials are the secrets or second factors a user presents to prove their identity. Keycloak supports passwords, OTP codes, passkeys, and more. Each credential type has its own priority and lifecycle.

Required actions are tasks Keycloak forces a user to complete before they can fully log in — for example, verifying their email address or setting a new password after an admin reset.

What is a user in Keycloak?
What is the main purpose of groups in Keycloak?
What is a required action in Keycloak?