无法使用 smalrye jwt 生成令牌

Posted 2023-03-10

技术标签:

【中文标题】无法使用 smalrye jwt 生成令牌【英文标题】：Unable to generate token using smalrye jwt 【发布时间】：2022-01-14 17:47:18 【问题描述】：

我刚开始使用 Quarkus。所以我想在我的演示应用程序中使用 smalrye jwt 生成一个令牌，但是当我尝试向此端点发出 GET 请求以获取令牌 http://localhost:8080/generate-token 时，它一直失败，并带有以下错误消息：

org.jboss.resteasy.spi.UnhandledException: io.smallrye.jwt.build.JwtSignatureException: SRJWT05009: 
        at org.jboss.resteasy.core.ExceptionHandler.handleApplicationException(ExceptionHandler.java:105)
        at org.jboss.resteasy.core.ExceptionHandler.handleException(ExceptionHandler.java:359)
        at org.jboss.resteasy.core.SynchronousDispatcher.writeException(SynchronousDispatcher.java:218)
        at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:519)
        at org.jboss.resteasy.core.SynchronousDispatcher.lambda$invoke$4(SynchronousDispatcher.java:261)
        at org.jboss.resteasy.core.SynchronousDispatcher.lambda$preprocess$0(SynchronousDispatcher.java:161)
        at org.jboss.resteasy.core.interception.jaxrs.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:364)
        at org.jboss.resteasy.core.SynchronousDispatcher.preprocess(SynchronousDispatcher.java:164)
        at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:247)
        at io.quarkus.resteasy.runtime.standalone.RequestDispatcher.service(RequestDispatcher.java:73)
        at io.quarkus.resteasy.runtime.standalone.VertxRequestHandler.dispatch(VertxRequestHandler.java:135)
        at io.quarkus.resteasy.runtime.standalone.VertxRequestHandler$1.run(VertxRequestHandler.java:90)
        at io.quarkus.vertx.core.runtime.VertxCoreRecorder$13.runWith(VertxCoreRecorder.java:543)
        at org.jboss.threads.EnhancedQueueExecutor$Task.run(EnhancedQueueExecutor.java:2449)
        at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1478)
        at org.jboss.threads.DelegatingRunnable.run(DelegatingRunnable.java:29)
        at org.jboss.threads.ThreadLocalResettingRunnable.run(ThreadLocalResettingRunnable.java:29)
        at io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30)
        at java.base/java.lang.Thread.run(Thread.java:834)
Caused by: io.smallrye.jwt.build.JwtSignatureException: SRJWT05009: 
        at io.smallrye.jwt.build.impl.JwtSignatureImpl.sign(JwtSignatureImpl.java:76)
        at com.beita.TokenService.generateToken(TokenService.java:24)
        at com.beita.TokenService_Subclass.generateToken$$superforward1(Unknown Source)
        at com.beita.TokenService_Subclass$$function$$2.apply(Unknown Source)
        at io.quarkus.arc.impl.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:54)
        at io.quarkus.arc.runtime.devconsole.InvocationInterceptor.proceed(InvocationInterceptor.java:62)
        at io.quarkus.arc.runtime.devconsole.InvocationInterceptor.monitor(InvocationInterceptor.java:49)
        at io.quarkus.arc.runtime.devconsole.InvocationInterceptor_Bean.intercept(Unknown Source)
        at io.quarkus.arc.impl.InterceptorInvocation.invoke(InterceptorInvocation.java:41)
        at io.quarkus.arc.impl.AroundInvokeInvocationContext.perform(AroundInvokeInvocationContext.java:41)
        at io.quarkus.arc.impl.InvocationContexts.performAroundInvoke(InvocationContexts.java:32)
        at com.beita.TokenService_Subclass.generateToken(Unknown Source)
        at com.beita.TokenService_ClientProxy.generateToken(Unknown Source)
        at com.beita.LoginResource.login(LoginResource.java:23)
        at com.beita.LoginResource_Subclass.login$$superforward1(Unknown Source)
        at com.beita.LoginResource_Subclass$$function$$2.apply(Unknown Source)
        at io.quarkus.arc.impl.AroundInvokeInvocationContext.proceed(AroundInvokeInvocationContext.java:54)
        at io.quarkus.arc.runtime.devconsole.InvocationInterceptor.proceed(InvocationInterceptor.java:62)
        at io.quarkus.arc.runtime.devconsole.InvocationInterceptor.monitor(InvocationInterceptor.java:49)
        at io.quarkus.arc.runtime.devconsole.InvocationInterceptor_Bean.intercept(Unknown Source)
        at io.quarkus.arc.impl.InterceptorInvocation.invoke(InterceptorInvocation.java:41)
        at io.quarkus.arc.impl.AroundInvokeInvocationContext.perform(AroundInvokeInvocationContext.java:41)
        at io.quarkus.arc.impl.InvocationContexts.performAroundInvoke(InvocationContexts.java:32)
        at com.beita.LoginResource_Subclass.login(Unknown Source)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
        at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.base/java.lang.reflect.Method.invoke(Method.java:566)
        at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:170)
        at org.jboss.resteasy.core.MethodInjectorImpl.invoke(MethodInjectorImpl.java:130)
        at org.jboss.resteasy.core.ResourceMethodInvoker.internalInvokeOnTarget(ResourceMethodInvoker.java:660)
        at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTargetAfterFilter(ResourceMethodInvoker.java:524)
        at org.jboss.resteasy.core.ResourceMethodInvoker.lambda$invokeOnTarget$2(ResourceMethodInvoker.java:474)
        at org.jboss.resteasy.core.interception.jaxrs.PreMatchContainerRequestContext.filter(PreMatchContainerRequestContext.java:364)
        at org.jboss.resteasy.core.ResourceMethodInvoker.invokeOnTarget(ResourceMethodInvoker.java:476)
        at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:434)
        at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:408)
        at org.jboss.resteasy.core.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:69)
        at org.jboss.resteasy.core.SynchronousDispatcher.invoke(SynchronousDispatcher.java:492)
        ... 15 more
Caused by: java.lang.IllegalArgumentException: SRJWT05020: Signing key can not be loaded from: privateKey.pem 
        at io.smallrye.jwt.build.impl.JwtSignatureImpl.getSigningKeyFromKeyLocation(JwtSignatureImpl.java:241)
        at io.smallrye.jwt.build.impl.JwtSignatureImpl.sign(JwtSignatureImpl.java:71)

这就是我正在做的。

application.properties

mp.jwt.verify.publickey.location=publicKey.pem
smallrye.jwt.sign.key.location=privateKey.pem 
mp.jwt.verify.issuer=https://example.com/issuer

TokenService.java

@RequestScoped
public class TokenService 
    public String generateToken()
        return Jwt.issuer("https://example.com/issuer") 
            .upn("johndoe@gmail.com")
            .groups(new HashSet<>(Arrays.asList("User", "Admin"))) 
            .expiresIn(300L)
            .claim(Claims.birthdate.name(), "2001-07-13") 
        .sign();

TokenResource.java

@Path("generate-token")
@Produces(MediaType.APPLICATION_JSON)
@Consumes(MediaType.APPLICATION_JSON)
public class TokenResource 

    @Inject
    TokenService tokenService;

    @GET
    public Response getToken()
        String token = tokenService.generateToken();
        return Response.ok(token).build();

登录资源

@Path("/auth")
public class LoginResource 
    
    @GET
    @Path("permit-all")
    @PermitAll
    @javax.ws.rs.Produces(MediaType.TEXT_PLAIN)
    public String hello() 
        return "hello";
    

    @Path("roles-allowed") 
    @RolesAllowed( "User", "Admin" )
    public String helloSecured() 
        return "hello admin or user";

我在 pom.xml 中有 quarkus-smallrye-jwt 依赖项

POM.xml

<dependency>
      <groupId>io.quarkus</groupId>
      <artifactId>quarkus-smallrye-jwt</artifactId>
</dependency>

我的 privateKey.pem 和 publicKey.pem 都在 resources 目录中。

publicKey.pem

privateKey.pem

【问题讨论】：

【参考方案1】：

你的application.properties这一行有一个尾随空格：

smallrye.jwt.sign.key.location=privateKey.pem

删除空间，它应该可以工作。见https://github.com/quarkusio/quarkus-quickstarts/blob/main/security-jwt-quickstart/src/main/resources/application.properties

【讨论】：

【参考方案2】：

这肯定是您的关键路径。仔细检查您的 pk 文件是否位于正确的位置，并且您的 application.properties 中没有尾随的白色字符。

【讨论】：

您的答案可以通过额外的支持信息得到改进。请edit 添加更多详细信息，例如引用或文档，以便其他人可以确认您的答案是正确的。你可以找到更多关于如何写好答案的信息in the help center。

以上是关于无法使用 smalrye jwt 生成令牌的主要内容，如果未能解决你的问题，请参考以下文章

无法使用 JWT 令牌连接到 Apple App Store API

Auth0 java-jwt 库无法验证有效令牌

使用 Jwt 的基于令牌的身份验证无法授权

Spring Boot + Security + JWT 无法生成令牌

在身份验证期间使用 JWT 令牌反序列化 cookie 无法正确反序列化

从 facebook 令牌到 jwt 令牌