SUPER_ADMIN_USERS
) with default user roles. After importing, add an admin user to the group and assign the necessary roles.
Make sure to validate the imported roles by checking the following section:
FLOWX_SUPER_USERS
.platform-authenticate
client - will be used for login/logout/refresh token by web and mobile apps.
{example}-authenticate
, which will be used for login, logout, and refresh token operations.openid-connect
.{example}-authenticate
client.realm-groups
: This mapper can be utilized to map user groups to the authorization token.business filter mapper
: Use this mapper to map custom attributes, for example, mapping the businessFilters list, to the token claim.realm-roles
: This mapper enables mapping a user’s realm role to a token claim.{example}-authenticate
groups
.{example}-authenticate
, and navigate to the Mappers section.{example}-authenticate
client - so roles will be available on the OAuth user info response.
To add a roles mapper, follow these steps:
{example}-authenticate
, and navigate to the Mappers section.{example}-platform-authorize
client - it will be used to authorize rest requests to microservices and Kafka
{example}-platform-authorize
client will be created and can be used to authorize REST requests to microservices and Kafka within your application.
realm-management
.FLOWX_ROLE
and role mapper), and access data from Keycloak.”FLOWX_ROLE
.FLOWX_ROLE
(this is needed to run process instances).FLOWX_ROLE
as service account role (this is needed to run process instances).