Comment 5 for bug 1578327

This report just caught my attention this morning.

The short answer is that the first 2 scenarios produce functional errors - we have parsed the request and tried to process it but failed. Last scenario - we could not even parse the request (one of the expected inputs was not in the expected format, i.e. 'user-' prefix was missing from the tag).

Longer answer, by looking at API call itself:

    Login(req params.LoginRequest) (params.LoginResult, error)

The first 2 scenarios have output - params.LoginResult where 2nd output parameter, error, is nil. So authentication was not successful - valid input was provided but the input was not correct.
The last scenario has 2nd output parameter, error, is not nil because calling the method itself has failed - malformed input was provided, it was not a valid method call.