You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2019-09-27 17:55:34,620 WARN [io.sma.jwt.aut.pri.DefaultJWTTokenParser] (vert.x-eventloop-thread-12) Token is invalid: JWT processing failed. Additional details: [[17] Unable to process JOSE object (cause: org.jose4j.lang.UnresolvableKeyException: Failed to resolve a key from: META-INF/resources/publicKey.pem): JsonWebSignature{"kid":"\/privateKey.pem","typ":"JWT","alg":"RS256"}->eyJraWQiOiJcL3ByaXZhdGVLZXkucGVtIiwidHlwIjoiSldUIiwiYWxnIjoiUlMyNTYifQ.eyJzdWIiOiJqZG9lLXVzaW5nLWp3dC1yYmFjIiwiYXVkIjoidXNpbmctand0LXJiYWMiLCJ1cG4iOiJqZG9lQHF1YXJrdXMuaW8iLCJiaXJ0aGRhdGUiOiIyMDAxLTA3LTEzIiwiYXV0aF90aW1lIjoxNTY5NTk5NzM0LCJpc3MiOiJodHRwczpcL1wvcXVhcmt1cy5pb1wvdXNpbmctand0LXJiYWMiLCJyb2xlTWFwcGluZ3MiOnsiZ3JvdXAyIjoiR3JvdXAyTWFwcGVkUm9sZSIsImdyb3VwMSI6Ikdyb3VwMU1hcHBlZFJvbGUifSwiZ3JvdXBzIjpbIkVjaG9lciIsIlRlc3RlciIsIlN1YnNjcmliZXIiLCJncm91cDIiXSwicHJlZmVycmVkX3VzZXJuYW1lIjoiamRvZSIsImV4cCI6MTU2OTYwMDAzNCwiaWF0IjoxNTY5NTk5NzM0LCJqdGkiOiJhLTEyMyJ9.Orn6q46XwbcQN8heUeXI9he9loRwTfbsGJFV8nnbxizhcppeKt8b5EA3VPb-Fvo-4uDL2Tu388MbqJKypyEdcKCpmMugbUrNpuiDRlQIoHJalb9wG7YAQwwdjlwKuFCsfVnH3Jju39eyh7W5LxoenpCRlg9x3GU2HuHXMHC9KJMtXWvyHoNfmomhs6NZ1Z85xyYGf-gxAP7_XJuml7oBwNUqgF3lJpATEaMinaAiBSHWj4DEa2_Jb0FAA4FdPbhyimYsCTIF1LRFXf7n8KwGrq3YSY8STsk66dYVG5l__-jsYM3lV_mqanGvpTCd8zf3y2bL4K2yH6Sy_F1XgtnEaw]
The text was updated successfully, but these errors were encountered:
@cescoffier thank you, I've added myself to the assignee list @kenfinnigan Hi Ken if you'd like to remain in the list of assignees then please stay :-)
@cescoffier Hi Clement, I've built a quarkus master, and run this demo in the development branch and it works fine in a native mode, after I updated the pom.xml to enable a native profile (actually, I had to disable this test - but it is unrelated to smallrye-jwt, to do with the subresources)
It's unable to find the pem file:
The text was updated successfully, but these errors were encountered: