-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Multiple Errors returned by the SDK have the same "Type" and "Code" #274
Comments
Thank you for your concern, we will take a look how we can make error descriptions more useful. |
Internal ref OKTA-435834 |
@NikitaAvraimov-okta Hi, this feedback was from me. I've been advised by Fei a while ago that the SDK returns this generic "Invalid status code 400 Bad Request" instead of "TYPE_OAUTH_TOKEN_ERROR". Please confirm whether this fix will address that as it is by far our biggest error. I'm concerned that issues other than token expiry are returning this 400 bad request, which we interpret as an expired token. |
@thereallukesimpson "TYPE_OAUTH_TOKEN_ERROR" is what we expect to respond with now |
when refreshing tokens we are also getting the "Invalid status code 400" error instead of a more descriptive I traced the error to the usage of the |
Hi @NikitaAvraimov-okta. Is there an upcoming release containing this fix? |
The fix from #293 has been released. |
Hi @JayNewstrom and @NikitaAvraimov-okta. Can you please confirm both the error type and structure that will now be returned for the other ambiguous error listed above: Also, can you please confirm that the structure of the error for
i.e.
|
@thereallukesimpson when refresh token is non-existent i.e. null when trying to refresh it exception looks like: |
Error types and codes are not implemented within the SDK as we have seen multiple errors returning "type":0,"code":0" .
Ex :
Other than reading the description field, how can we differentiate between these two errors?
The text was updated successfully, but these errors were encountered: