Skip to content

Commit 095462d

Browse files
authored
Merge pull request #49885 from rolfedh/fix-additional-typos
Fix typos and make minor copyedits in the OIDC auth documentation
2 parents 2219469 + 37b0702 commit 095462d

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/src/main/asciidoc/security-oidc-bearer-token-authentication.adoc

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -603,7 +603,7 @@ testImplementation("io.quarkus:quarkus-junit5")
603603

604604
The preferred approach for integration testing against Keycloak is xref:security-openid-connect-dev-services.adoc[Dev Services for Keycloak].
605605
`Dev Services for Keycloak` will start and initialize a test container.
606-
Then, it will create a `quarkus` realm and a `quarkus-app` client (`secret` secret) and add `alice` (`admin` and `user` roles) and `bob` (`user` role) users, where all of these properties can be customized.
606+
Then, it will create a `quarkus` realm and a `quarkus-app` client with `secret` as the client secret. It will also add two users: `alice` with both `admin` and `user` roles, and `bob` with the `user` role. All of these properties can be customized.
607607

608608
First, add the following dependency, which provides a utility class `io.quarkus.test.keycloak.client.KeycloakTestClient` that you can use in tests for acquiring the access tokens:
609609

@@ -626,7 +626,7 @@ testImplementation("io.quarkus:quarkus-test-keycloak-server")
626626
Next, prepare your `application.properties` configuration file.
627627
You can start with an empty `application.properties` file because `Dev Services for Keycloak` registers `quarkus.oidc.auth-server-url` and points it to the running test container, `quarkus.oidc.client-id=quarkus-app`, and `quarkus.oidc.credentials.secret=secret`.
628628

629-
However, if you have already configured the required `quarkus-oidc` properties, then you only need to associate `quarkus.oidc.auth-server-url` with the `prod` profile for `Dev Services for Keycloak`to start a container, as shown in the following example:
629+
However, if you have already configured the required `quarkus-oidc` properties, then you only need to associate `quarkus.oidc.auth-server-url` with the `prod` profile for `Dev Services for Keycloak` to start a container, as shown in the following example:
630630

631631
[source,properties]
632632
----

0 commit comments

Comments
 (0)