From 3e3fc9751b6f9933eb488460da6e8cd7cb8034b8 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Michel=20K=C3=A4ser?= Date: Tue, 2 Jul 2024 07:36:07 +0200 Subject: [PATCH] docs: wrong property in JWT key example --- docs/src/main/asciidoc/security-jwt-build.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/src/main/asciidoc/security-jwt-build.adoc b/docs/src/main/asciidoc/security-jwt-build.adoc index 34a51fec4e9cb..40273dc43543c 100644 --- a/docs/src/main/asciidoc/security-jwt-build.adoc +++ b/docs/src/main/asciidoc/security-jwt-build.adoc @@ -241,8 +241,8 @@ As mentioned above, `iat` (issued at), `exp` (expires at), `jti` (token identifi [source,properties] ---- -smallrye.jwt.sign.key=privateKey.pem -smallrye.jwt.encrypt.key=publicKey.pem +smallrye.jwt.sign.key.location=privateKey.pem +smallrye.jwt.encrypt.key.location=publicKey.pem ---- You can also use MicroProfile `ConfigSource` to fetch the keys from the external services such as link:{vault-guide}[HashiCorp Vault] or other secret managers and use `smallrye.jwt.sign.key` and `smallrye.jwt.encrypt.key` properties instead: