Skip to content

Handling 500 response from API #15

@wopsononock

Description

@wopsononock

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions