From a8b545bb162a10538e35cca5f45dd5ab16c426cb Mon Sep 17 00:00:00 2001 From: Sergey Beryozkin Date: Thu, 1 Oct 2020 18:56:01 +0100 Subject: [PATCH] Fix the private key location in the smallrye-jwt guide --- docs/src/main/asciidoc/security-jwt.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/main/asciidoc/security-jwt.adoc b/docs/src/main/asciidoc/security-jwt.adoc index 3382b4b04ad36..06eabaa6b3b04 100644 --- a/docs/src/main/asciidoc/security-jwt.adoc +++ b/docs/src/main/asciidoc/security-jwt.adoc @@ -374,7 +374,7 @@ in order for the token to be accepted as valid. <3> The `group` claim provides the groups and top-level roles associated with the JWT bearer. <4> The `birthday` claim. It can be considered to be a sensitive claim so you may want to consider encrypting the claims, see <>. -Note for this code to work we need the content of the RSA private key that corresponds to the public key we have in the TokenSecuredResource application. Take the following PEM content and place it into `security-jwt-quickstart/src/main/resources/META-INF/resources/privateKey.pem`: +Note for this code to work we need the content of the RSA private key that corresponds to the public key we have in the TokenSecuredResource application. Take the following PEM content and place it into `security-jwt-quickstart/src/test/resources/privateKey.pem`: .RSA Private Key PEM Content [source, text]