Purpose
This article explains, at a high level, how authentication works in the platform through OAuth2 and Keycloak.
Overview
The platform uses Keycloak as its identity provider. In practice, authentication means that a client sends user credentials or follows a login flow, Keycloak verifies the user, and then returns an access token that the application can use to call protected services. Keycloak exposes standard OpenID Connect endpoints and supports OAuth 2.0-based authentication flows for applications and services.
How it works
At a conceptual level, the authentication flow is simple:
- the user provides credentials, or is redirected to Keycloak for login
- Keycloak authenticates the user
- Keycloak issues an access token
- the application uses that token to access protected APIs or services
In many deployments, this is implemented with OpenID Connect on top of OAuth 2.0, which is the standard way Keycloak secures applications and services.
What Keycloak provides
Keycloak acts as the central identity layer for the platform. It can:
- authenticate users
- issue tokens
- manage realms, users, and roles
- integrate with external identity providers
- secure applications through standard protocols
Because Keycloak is standards-based, the authentication model is familiar and interoperable with common enterprise identity setups.
Access token concept
The most important output of authentication is the access token. This token represents the authenticated session and is what downstream services rely on when deciding whether a request is authenticated.
In other words, applications generally do not re-check the user’s password on every request. They validate the token issued by Keycloak.
Typical platform usage
In the platform, the practical mental model is:
- the user authenticates through Keycloak
- Keycloak returns an access token
- that token is then used to call platform APIs and protected services
This keeps authentication centralized and avoids reimplementing login logic in each service.
User Management in Keycloak
Purpose
This article explains how user management is handled in Keycloak and where administrators can manage users and roles for the platform. Please refer to Keycload's official documentation for further details.
Overview
User management is handled in Keycloak. In your setup, the main place to look is the giotto realm, where administrators can view users, assign roles, and manage the identities that are allowed to access the platform.
This is standard Keycloak administration: realms provide isolation, while users and roles are managed within the selected realm. Keycloak’s admin model and documentation are organized around exactly these concepts.
Where to go
To manage users:
- open the Keycloak admin console
- select the
giottorealm - open the Users section to browse or search users
- open the Roles section to inspect available roles
This is the main administrative entry point for platform access management.
What you can manage
Within the giotto realm, administrators typically manage:
- platform users
- role assignments
- user details and profile information
- identity-related settings tied to access control
The most important operational objects are usually:
- users, which represent the people or identities accessing the platform
- roles, which are later used by authorization layers such as Authz
Realms, users, and roles
A useful way to think about the structure is:
- the realm is the security boundary for the platform
- users are the identities inside that realm
- roles are the labels or permissions groups attached to users
This separation is important because authentication happens through Keycloak, but authorization decisions are often based on the roles Keycloak provides.
Typical administrative tasks
Common user management actions include:
- finding a user in the
giottorealm - creating or updating a user
- assigning or removing roles
- verifying whether a user belongs to the expected role set
These are standard Keycloak operations and are well covered by the Keycloak administration docs.
How this connects to the platform
In the platform, Keycloak is the source of truth for user identity. When a user authenticates successfully, their identity and assigned roles can be used by downstream services to determine what they are allowed to access.
That means user management in Keycloak directly affects platform access.
Comments
0 comments
Article is closed for comments.