gvama (gvama) asked a question.
Upgrading jwt-verifier to latest version
Hi, we are upgrading the jwt-verifier java library from 0.3.0 to the latest version 0.5.1. In the old version we were able to set the clientId in the JwtVerifier like this
JwtHelper jwtBuilder = new JwtHelper().setClientId(clientId);
and later try to decode the access token via
Jwt jwt = jwtVerifier.decodeAccessToken(accessToken);
But since the newer version 0.4.0 came out, the new class JwtVerifiers.accessTokenVerifierBuilder doesn't have option to set the clientId.
Does this mean we can no longer use clientId as part of decode accesstoken?
Thank you,
Petch
Hello @gvama (gvama)
I hope you are having a great day
Thank you for posting, since the new version does not include the new class the old configuration may not work.
to know more about this topic you can check the following link: https://developer.okta.com/code/dotnet/jwt-validation/#additional-validation-for-access-tokens
If you need further assistance you can also feel free to post this question on our Okta Developer Forums: https://devforum.okta.com, this is a place for the Okta developer community to interact
Have a great day ahead
Henry E.
Okta Inc
Hello,
could we know how to solve?
We must keep using 0.3x version forever or is there a solution/new approach to obtain the same result?
I followed the "old" JavaEE implementation and I faced with the same problem.
Is there a more recent developer-guide?
(I mentioned this one:
https://developer.okta.com/blog/2018/09/12/secure-java-ee-rest-api )
Thank you
Daniele