Sync documentation of main branch

Author: actions-user

_generated-doc/main/config/quarkus-all-config.adoc

@@ -69611,7 +69611,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Decryption key location. JWT tokens can be inner-signed and encrypted by OpenId Connect providers. However, it is not always possible to remotely introspect such tokens because the providers might not control the private decryption keys. In such cases set this property to point to the file containing the decryption private key in PEM or JSON Web Key (JWK) format. If this property is not set and the `private_key_jwt` client authentication method is used, the private key used to sign the client authentication JWT tokens are also used to decrypt the encrypted ID tokens.
+Decryption key location for encrypted ID and access tokens.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -69624,6 +69624,58 @@ endif::add-copy-button-to-env-var[]
 |string
 |
 
+a| [[quarkus-oidc_quarkus-oidc-token-decrypt-id-token]] [.property-path]##link:#quarkus-oidc_quarkus-oidc-token-decrypt-id-token[`quarkus.oidc.token.decrypt-id-token`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc.token.decrypt-id-token+++[]
+endif::add-copy-button-to-config-props[]
+
+
+`quarkus.oidc."tenant".token.decrypt-id-token`
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc."tenant".token.decrypt-id-token+++[]
+endif::add-copy-button-to-config-props[]
+
+[.description]
+--
+Decrypt ID token. If the `Token++#++decryptionKeyLocation()` property is configured then the decryption key will be loaded from this location. Otherwise, if the JWT authentication token key is available, then it will be used to decrypt the token. Finally, if a client secret is configured, it will be used as a secret key to decrypt the token.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_OIDC_TOKEN_DECRYPT_ID_TOKEN+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_OIDC_TOKEN_DECRYPT_ID_TOKEN+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|
+
+a| [[quarkus-oidc_quarkus-oidc-token-decrypt-access-token]] [.property-path]##link:#quarkus-oidc_quarkus-oidc-token-decrypt-access-token[`quarkus.oidc.token.decrypt-access-token`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc.token.decrypt-access-token+++[]
+endif::add-copy-button-to-config-props[]
+
+
+`quarkus.oidc."tenant".token.decrypt-access-token`
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc."tenant".token.decrypt-access-token+++[]
+endif::add-copy-button-to-config-props[]
+
+[.description]
+--
+Decrypt access token. If the `Token++#++decryptionKeyLocation()` property is configured then the decryption key will be loaded from this location. Otherwise, if the JWT authentication token key is available, then it will be used to decrypt the token. Finally, if a client secret is configured, it will be used as a secret key to decrypt the token.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_OIDC_TOKEN_DECRYPT_ACCESS_TOKEN+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_OIDC_TOKEN_DECRYPT_ACCESS_TOKEN+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`false`
+
 a| [[quarkus-oidc_quarkus-oidc-token-allow-jwt-introspection]] [.property-path]##link:#quarkus-oidc_quarkus-oidc-token-allow-jwt-introspection[`quarkus.oidc.token.allow-jwt-introspection`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.oidc.token.allow-jwt-introspection+++[]

_generated-doc/main/config/quarkus-oidc.adoc

@@ -2243,7 +2243,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Decryption key location. JWT tokens can be inner-signed and encrypted by OpenId Connect providers. However, it is not always possible to remotely introspect such tokens because the providers might not control the private decryption keys. In such cases set this property to point to the file containing the decryption private key in PEM or JSON Web Key (JWK) format. If this property is not set and the `private_key_jwt` client authentication method is used, the private key used to sign the client authentication JWT tokens are also used to decrypt the encrypted ID tokens.
+Decryption key location for encrypted ID and access tokens.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -2256,6 +2256,58 @@ endif::add-copy-button-to-env-var[]
 |string
 |
 
+a| [[quarkus-oidc_quarkus-oidc-token-decrypt-id-token]] [.property-path]##link:#quarkus-oidc_quarkus-oidc-token-decrypt-id-token[`quarkus.oidc.token.decrypt-id-token`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc.token.decrypt-id-token+++[]
+endif::add-copy-button-to-config-props[]
+
+
+`quarkus.oidc."tenant".token.decrypt-id-token`
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc."tenant".token.decrypt-id-token+++[]
+endif::add-copy-button-to-config-props[]
+
+[.description]
+--
+Decrypt ID token. If the `Token++#++decryptionKeyLocation()` property is configured then the decryption key will be loaded from this location. Otherwise, if the JWT authentication token key is available, then it will be used to decrypt the token. Finally, if a client secret is configured, it will be used as a secret key to decrypt the token.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_OIDC_TOKEN_DECRYPT_ID_TOKEN+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_OIDC_TOKEN_DECRYPT_ID_TOKEN+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|
+
+a| [[quarkus-oidc_quarkus-oidc-token-decrypt-access-token]] [.property-path]##link:#quarkus-oidc_quarkus-oidc-token-decrypt-access-token[`quarkus.oidc.token.decrypt-access-token`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc.token.decrypt-access-token+++[]
+endif::add-copy-button-to-config-props[]
+
+
+`quarkus.oidc."tenant".token.decrypt-access-token`
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc."tenant".token.decrypt-access-token+++[]
+endif::add-copy-button-to-config-props[]
+
+[.description]
+--
+Decrypt access token. If the `Token++#++decryptionKeyLocation()` property is configured then the decryption key will be loaded from this location. Otherwise, if the JWT authentication token key is available, then it will be used to decrypt the token. Finally, if a client secret is configured, it will be used as a secret key to decrypt the token.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_OIDC_TOKEN_DECRYPT_ACCESS_TOKEN+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_OIDC_TOKEN_DECRYPT_ACCESS_TOKEN+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`false`
+
 a| [[quarkus-oidc_quarkus-oidc-token-allow-jwt-introspection]] [.property-path]##link:#quarkus-oidc_quarkus-oidc-token-allow-jwt-introspection[`quarkus.oidc.token.allow-jwt-introspection`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.oidc.token.allow-jwt-introspection+++[]

_generated-doc/main/config/quarkus-oidc_quarkus.oidc.adoc

@@ -2243,7 +2243,7 @@ endif::add-copy-button-to-config-props[]
 
 [.description]
 --
-Decryption key location. JWT tokens can be inner-signed and encrypted by OpenId Connect providers. However, it is not always possible to remotely introspect such tokens because the providers might not control the private decryption keys. In such cases set this property to point to the file containing the decryption private key in PEM or JSON Web Key (JWK) format. If this property is not set and the `private_key_jwt` client authentication method is used, the private key used to sign the client authentication JWT tokens are also used to decrypt the encrypted ID tokens.
+Decryption key location for encrypted ID and access tokens.
 
 
 ifdef::add-copy-button-to-env-var[]
@@ -2256,6 +2256,58 @@ endif::add-copy-button-to-env-var[]
 |string
 |
 
+a| [[quarkus-oidc_quarkus-oidc-token-decrypt-id-token]] [.property-path]##link:#quarkus-oidc_quarkus-oidc-token-decrypt-id-token[`quarkus.oidc.token.decrypt-id-token`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc.token.decrypt-id-token+++[]
+endif::add-copy-button-to-config-props[]
+
+
+`quarkus.oidc."tenant".token.decrypt-id-token`
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc."tenant".token.decrypt-id-token+++[]
+endif::add-copy-button-to-config-props[]
+
+[.description]
+--
+Decrypt ID token. If the `Token++#++decryptionKeyLocation()` property is configured then the decryption key will be loaded from this location. Otherwise, if the JWT authentication token key is available, then it will be used to decrypt the token. Finally, if a client secret is configured, it will be used as a secret key to decrypt the token.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_OIDC_TOKEN_DECRYPT_ID_TOKEN+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_OIDC_TOKEN_DECRYPT_ID_TOKEN+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|
+
+a| [[quarkus-oidc_quarkus-oidc-token-decrypt-access-token]] [.property-path]##link:#quarkus-oidc_quarkus-oidc-token-decrypt-access-token[`quarkus.oidc.token.decrypt-access-token`]##
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc.token.decrypt-access-token+++[]
+endif::add-copy-button-to-config-props[]
+
+
+`quarkus.oidc."tenant".token.decrypt-access-token`
+ifdef::add-copy-button-to-config-props[]
+config_property_copy_button:+++quarkus.oidc."tenant".token.decrypt-access-token+++[]
+endif::add-copy-button-to-config-props[]
+
+[.description]
+--
+Decrypt access token. If the `Token++#++decryptionKeyLocation()` property is configured then the decryption key will be loaded from this location. Otherwise, if the JWT authentication token key is available, then it will be used to decrypt the token. Finally, if a client secret is configured, it will be used as a secret key to decrypt the token.
+
+
+ifdef::add-copy-button-to-env-var[]
+Environment variable: env_var_with_copy_button:+++QUARKUS_OIDC_TOKEN_DECRYPT_ACCESS_TOKEN+++[]
+endif::add-copy-button-to-env-var[]
+ifndef::add-copy-button-to-env-var[]
+Environment variable: `+++QUARKUS_OIDC_TOKEN_DECRYPT_ACCESS_TOKEN+++`
+endif::add-copy-button-to-env-var[]
+--
+|boolean
+|`false`
+
 a| [[quarkus-oidc_quarkus-oidc-token-allow-jwt-introspection]] [.property-path]##link:#quarkus-oidc_quarkus-oidc-token-allow-jwt-introspection[`quarkus.oidc.token.allow-jwt-introspection`]##
 ifdef::add-copy-button-to-config-props[]
 config_property_copy_button:+++quarkus.oidc.token.allow-jwt-introspection+++[]