Conditionalize references to OAuth2

quarkusio · Jan 7, 2025 · e4eb20c · e4eb20c
1 parent 0e013fa
commit e4eb20c
Show file tree

Hide file tree

Showing 2 changed files with 16 additions and 1 deletion.
diff --git a/docs/src/main/asciidoc/security-authentication-mechanisms.adoc b/docs/src/main/asciidoc/security-authentication-mechanisms.adoc
@@ -402,7 +402,12 @@ For more information about managing the individual tenant configurations in mult
 
 ==== OpenID Connect client and filters
 
+ifndef::no-quarkus-elytron-security-oauth2[]
 The `quarkus-oidc-client` extension provides `OidcClient` for acquiring and refreshing access tokens from OpenID Connect and OAuth2 providers that support the following token grants:
+endif::no-quarkus-elytron-security-oauth2[]
+ifdef::no-quarkus-elytron-security-oauth2[]
+The `quarkus-oidc-client` extension provides `OidcClient` for acquiring and refreshing access tokens from OpenID Connect providers that support the following token grants:
+endif::no-quarkus-elytron-security-oauth2[]
 
 * `client-credentials`
 * `password`
@@ -448,7 +453,12 @@ For more information, see the Quarkus xref:security-oauth2.adoc[Using OAuth2] gu
 endif::no-quarkus-elytron-security-oauth2[]
 
 [[oidc-jwt-oauth2-comparison]]
+ifndef::no-quarkus-elytron-security-oauth2[]
 == Choosing between OpenID Connect, SmallRye JWT, and OAuth2 authentication mechanisms
+endif::no-quarkus-elytron-security-oauth2[]
+ifdef::no-quarkus-elytron-security-oauth2[]
+== Choosing between OpenID Connect and SmallRye JWT authentication mechanisms
+endif::no-quarkus-elytron-security-oauth2[]
 
 Use the following information to select the appropriate token authentication mechanism to secure your Quarkus applications.
 

diff --git a/docs/src/main/asciidoc/security-identity-providers.adoc b/docs/src/main/asciidoc/security-identity-providers.adoc
@@ -17,7 +17,12 @@ In the Quarkus Security framework, identity providers play a crucial role in aut
 [[identity-providers]]
 `IdentityProvider` converts the authentication credentials provided by `HttpAuthenticationMechanism` to a `SecurityIdentity` instance.
 
-Some extensions, for example, `OIDC`, `OAuth2`, and `SmallRye JWT`, have inline `IdentityProvider` implementations specific to the supported authentication flow.
+ifndef::no-quarkus-elytron-security-oauth2[]
+Some extensions, such as `OIDC`, `OAuth2`, and `SmallRye JWT`, include inline `IdentityProvider` implementations specific to their supported authentication flows.
+endif::no-quarkus-elytron-security-oauth2[]
+ifdef::no-quarkus-elytron-security-oauth2[]
+Some extensions, such as `OIDC` and `SmallRye JWT`, include inline `IdentityProvider` implementations specific to their supported authentication flows.
+endif::no-quarkus-elytron-security-oauth2[]
 For example, `quarkus-oidc` uses its own `IdentityProvider` to convert a token to a `SecurityIdentity` instance.
 
 If you use Basic or form-based authentication, you must add an `IdentityProvider` instance to convert a username and password to a `SecurityIdentity` instance.