
User16304573516921762936 (Customer) asked a question.
I am getting an E0000011 Invalid Token Provided exception. Everything I've found says this is because the account that created the token is not active. But I created a new token and my account is definitely not inactive. BTW, I can log in using without issue from my local machine, but not from a QA box. Trusted Origins have been verified. Any thoughts?

Hi @User16304573516921762936 (Customer) , Thank you for reaching out to the Okta Community!
It's unclear what the context is for this. Where are you seeing this error?
Is this related to MFA authentication or some kind of API integration?
Regards.
--
Join the discussion for the Ask Me Anything online event on May 23, 2024 with Okta Tactical Edge Product Experts
@Mihai Negoita - Okta (Okta, Inc.) Sorry for the slow response on this. The problem went away, but now it has returned. The issue is with an API integration.
From our QA environment, when attempting to log in to a QA website using Okta, we are receiving either the error listed above, or the E0000015 error, but this is a dev org.
If I connect to the remote QA database from my local environment, I can log in without any problems. So I know we have the connection parameters set correctly in the database.
I, and others, have verified our trusted origins are correct, that the client id is active and that the API key is not expired.
We have engaged our networking and server personnel to make sure nothing odd is happening on our servers.
The most frustrating thing about this is that it comes and goes. It doesn't happen consistently.
Hi @User16304573516921762936 (Customer) , Thanks for the additional details.
This question is more appropriate for our dedicated Okta Developer Forum.
My advice would be to reach out via devforum.okta.com to take advantage of their expertise.
While we'll do our best to answer all of your questions here, this medium is more inclined towards Okta core products and features (non-custom/developer work).