From 3705b43b4bcaba8a4c8190745d1457ebc6e74c74 Mon Sep 17 00:00:00 2001 From: Yoshikazu Nojima Date: Fri, 31 May 2024 00:13:19 +0900 Subject: [PATCH] Correct broken markup in the security-customization.adoc --- docs/src/main/asciidoc/security-customization.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/main/asciidoc/security-customization.adoc b/docs/src/main/asciidoc/security-customization.adoc index 783e286622aea..5a0ee041e6672 100644 --- a/docs/src/main/asciidoc/security-customization.adoc +++ b/docs/src/main/asciidoc/security-customization.adoc @@ -74,7 +74,7 @@ public class CustomAwareJWTAuthMechanism implements HttpAuthenticationMechanism TIP: The `HttpAuthenticationMechanism` should transform incoming HTTP request with suitable authentication credentials into an `io.quarkus.security.identity.request.AuthenticationRequest` instance and delegate the authentication to the `io.quarkus.security.identity.IdentityProviderManager`. -Leaving authentication to the `io.quarkus.security.identity.IdentityProvider`s gives you more options for credentials verifications, +Leaving authentication to the ``io.quarkus.security.identity.IdentityProvider``s gives you more options for credentials verifications, as well as convenient way to perform blocking tasks. Nevertheless, the `io.quarkus.security.identity.IdentityProvider` can be omitted and the `HttpAuthenticationMechanism` is free to authenticate request on its own in trivial use cases. @@ -744,4 +744,4 @@ For that reason, asynchronous processing can have positive effect on performance * xref:security-overview.adoc[Quarkus Security overview] * xref:security-architecture.adoc[Quarkus Security architecture] * xref:security-authentication-mechanisms.adoc#other-supported-authentication-mechanisms[Authentication mechanisms in Quarkus] -* xref:security-identity-providers.adoc[Identity providers] \ No newline at end of file +* xref:security-identity-providers.adoc[Identity providers]