Client call fails with Okta E0000011

I have a Java backend of an app that calls the Okta API. I pass in a token, it passes the JwtVerifier.decodeAccessToken() call. Then, I attempt to make a call to Client.getUser().getProfile() and I get this error:

ERROR - HTTP 401, Okta E0000011 (Invalid token provided), ErrorId oaeOzaO_GyyTImLaMViGyYX7g
com.okta.sdk.resource.ResourceException: HTTP 401, Okta E0000011 (Invalid token provided), ErrorId oaeOzaO_GyyTImLaMViGyYX7g

All of this used to work, and I don’t understand what changed. As part of the debugging process, I upgraded the Okta java dependencies from 0.9.0 to 1.3.0

Any help would be appreciated.

It turned out to be an expired API token.

Yes, that gets me all the time too. Tokens are set to expire after a set amount of time. If you do not use them, they will expire and cause this kind of error.

AFAIK, there is no way to prevent this from happening.

This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.