diff --git a/index.html b/index.html index a78bb12..dd4d1c1 100644 --- a/index.html +++ b/index.html @@ -85,7 +85,7 @@

2.1. Architecture
  • - 2.2. RHBK Configuration + 2.2. RedHat Build of Keycloak Configuration
  • 2.3. Backend diff --git a/openid-jwt.html b/openid-jwt.html index 693998d..60f7b57 100644 --- a/openid-jwt.html +++ b/openid-jwt.html @@ -85,7 +85,7 @@

    2.1. Architecture
  • - 2.2. RHBK Configuration + 2.2. RedHat Build of Keycloak Configuration
  • 2.3. Backend @@ -125,7 +125,7 @@

    OpenID + JWT

    This tutorial demonstrates how to implement an OpenID Connect flow with a JWT implementation.

    -

    We will set up a new realm in Red Hat Build for Keycloak (RHBK) and configure it. Subsequently, we will deploy the stack and configure user access, enabling roles for various operations.

    +

    We will set up a new realm in Red Hat Build for Keycloak and configure it. Subsequently, we will deploy the stack and configure user access, enabling roles for various operations.

    @@ -133,7 +133,7 @@

    OpenID + JWT

    Architecture

    -

    Firstly, we require an instance of RHBK to manage access across our applications. One advantage of implementing OpenID Connect with JWT is the seamless integration of various applications and frameworks, facilitated by libraries available for each.

    +

    Firstly, we require an instance of Red Hat Build for Keycloak to manage access across our applications. One advantage of implementing OpenID Connect with JWT is the seamless integration of various applications and frameworks, facilitated by libraries available for each.

    In this instance, we will construct a comprehensive architecture involving several microservices. The frontend is developed in ReactJS, responsible for displaying the data.

    @@ -149,7 +149,7 @@

    Architecture

    -

    RHBK configuration

    +

    Red Hat Build for Keycloak configuration

    This section outlines the process of creating a new realm using the OpenID Connect flow and provides guidance on its configuration.

    @@ -157,7 +157,7 @@

    RHBK configuration

    Create a realm

    -

    A realm in RHBK functions as a domain where clients, users, roles, etc., can be configured. In this example, we offer an import containing the configuration to execute this workshop. Nevertheless, we are creating one from scratch to illustrate all the processes:

    +

    A realm in Red Hat Build for Keycloak functions as a domain where clients, users, roles, etc., can be configured. In this example, we offer an import containing the configuration to execute this workshop. Nevertheless, we are creating one from scratch to illustrate all the processes:

    @@ -168,7 +168,7 @@

    Create a

    Create a client

    -

    A client in RHBK serves as a consumer. Since we are employing an OpenID Connect flow, the selection of a standard or implicit flow depends on whether we are configuring a private or public client.

    +

    A client in Red Hat Build for Keycloak serves as a consumer. Since we are employing an OpenID Connect flow, the selection of a standard or implicit flow depends on whether we are configuring a private or public client.

    To register a new client, navigate to the Keycloak admin console and access the client options. In this section, locate the "Create client" option.

    @@ -218,7 +218,7 @@

    <

    -

    RHBK configuration

    +

    Red Hat Build for Keycloak configuration

    The Keycloak instance includes a realm that has been configured with a dedicated client tailored for this workshop.

    @@ -226,7 +226,7 @@

    R

    This application functions as a backend service utilizing a standard flow with a private client. In the upcoming section, you will find all the necessary configurations.

    -

    If you want to review the OpenID Connect client configuration and explore the RHBK admin console, please navigate to the following section.

    +

    If you want to review the OpenID Connect client configuration and explore the Red Hat Build for Keycloak admin console, please navigate to the following section.

    @@ -237,7 +237,7 @@

    R

    Quarkus configuration

    -

    Quarkus streamlines the security configuration in our backend services. To achieve this, we need to import the corresponding library. In this case, even though we are working with RHBK, since it follows the OpenID Connect protocol, we will utilize the quarkus-oidc generic library.

    +

    Quarkus streamlines the security configuration in our backend services. To achieve this, we need to import the corresponding library. In this case, even though we are working with Red Hat Build for Keycloak, since it follows the OpenID Connect protocol, we will utilize the quarkus-oidc generic library.

    @@ -301,7 +301,7 @@

    -

    To obtain an access token, we need to configure certain parameters that RHBK requires.

    +

    To obtain an access token, we need to configure certain parameters that Red Hat Build for Keycloak requires.

    @@ -448,7 +448,7 @@

    Create the user

    -

    The initial step is to create a new user to demonstrate the entire configuration step by step. To do this, enter the RHBK admin console, navigate to the "users" section, and click the "add user" button.

    +

    The initial step is to create a new user to demonstrate the entire configuration step by step. To do this, enter the Red Hat Build for Keycloak admin console, navigate to the "users" section, and click the "add user" button.

    @@ -580,7 +580,7 @@

    At this point, we understand how the ReactJS security model relies on the user roles present in the JWT token.

    -

    Now, let’s proceed to add roles to users to enable private actions. The initial step is to return to the RHBK admin page and locate the user named reader. Once you have identified the user, navigate to the "Role mapping" tab.

    +

    Now, let’s proceed to add roles to users to enable private actions. The initial step is to return to the Red Hat Build for Keycloak admin page and locate the user named reader. Once you have identified the user, navigate to the "Role mapping" tab.

    @@ -588,7 +588,7 @@

    -

    After clicking the "Assign role" button, RHBK will display a list of all available roles in the system.

    +

    After clicking the "Assign role" button, Red Hat Build for Keycloak will display a list of all available roles in the system.

    Select the role "padel-player" and click the "Assign" button.

    diff --git a/setup.html b/setup.html index 2975182..8df3b40 100644 --- a/setup.html +++ b/setup.html @@ -86,7 +86,7 @@

    2.1. Architecture
  • - 2.2. RHBK Configuration + 2.2. RedHat Build of Keycloak Configuration
  • 2.3. Backend diff --git a/sitemap.xml b/sitemap.xml index 924a021..d9a69ff 100644 --- a/sitemap.xml +++ b/sitemap.xml @@ -2,14 +2,14 @@ https://olleb.com/rhbk-workshop/index.html -2024-01-31T00:05:37.477Z +2024-04-23T22:10:31.201Z https://olleb.com/rhbk-workshop/openid-jwt.html -2024-01-31T00:05:37.477Z +2024-04-23T22:10:31.201Z https://olleb.com/rhbk-workshop/setup.html -2024-01-31T00:05:37.477Z +2024-04-23T22:10:31.201Z