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
java.lang.RuntimeException: Signature verification failed
at io.vertx.ext.auth.impl.jose.JWT.decode(JWT.java:312)
at io.vertx.ext.auth.impl.jose.JWT.decode(JWT.java:177)
at io.vertx.ext.auth.oauth2.impl.OAuth2AuthProviderImpl.createUser(OAuth2AuthProviderImpl.java:579)
at io.vertx.ext.auth.oauth2.impl.OAuth2AuthProviderImpl.lambda$authenticate$4(OAuth2AuthProviderImpl.java:457)
If you're a client getting a token for Graph, assume that it's an encrypted string that you should never look at
I think the offending code is this:
// attempt to decode tokens if jwt keys are available
if (!jwt.isUnsecure()) {
if (json.containsKey("access_token")) {
try {
final JsonObject token = jwt.decode(json.getString("access_token"));
The text was updated successfully, but these errors were encountered:
In fact requiring the access token to be a JWT already breaks the specification
Access tokens do not have to be of any particular format, although there are different considerations for different options which will be discussed later in this chapter.
Version
4.5.8
Context
I'm trying to authenticate against Graph API using client credentials flow.
Unfortunately it fails on:
Clients should not try to inspect access tokens at all. MSFT is right in stating:
I think the offending code is this:
The text was updated successfully, but these errors were encountered: