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
Submitting a login request to the iThenticate API with a blank username/password returns a response with a 500 status and no sid. iThenticate API documentation states that 401 is returned when no sid can be generated. Given this inconsistency, might we adapt the login method to throw an Exception on 500 or even any non 200 status?
There is an error message in the response I'm getting that actually spells out the fact that username and pass are required, so that could be used as an alternative signal of failure to login.
The text was updated successfully, but these errors were encountered:
Submitting a login request to the iThenticate API with a blank username/password returns a response with a 500 status and no sid. iThenticate API documentation states that 401 is returned when no sid can be generated. Given this inconsistency, might we adapt the login method to throw an Exception on 500 or even any non 200 status?
There is an error message in the response I'm getting that actually spells out the fact that username and pass are required, so that could be used as an alternative signal of failure to login.
The text was updated successfully, but these errors were encountered: