I'm opening this issue to highlight this change which took us a while to figure out. When trying to login via services we only got 401 errors when we used to get a successful login. There were no clues in the watchdog table nor in the response from the server.

Since this probably affects other users, I think the best fix would be to accept either username/password and/or user/pass for authentication for backwards and forwards compatibility.

CommentFileSizeAuthor
#5 2045297.patch1.32 KBrajarju

Comments

marcingy’s picture

marcingy commented
Category: bug » support
Priority: Major » Normal

This was changed in #1975054: Inconsistent parameters for user registration vs. user login using versioning if you need the old version you need to use old version of the API using a header.

marcingy’s picture

marcingy commented
Title: REST Server login argument names have changed from username and password to user and pass » The version API does not seem to use the original settings as default as per the docs
Category: support » bug
Priority: Normal » Major

Hmm actually on reading the docs more this an issue - issue title updated

kylebrowning’s picture

kylebrowning commented
Assigned: Unassigned » kylebrowning

Ill tak a look at this.

rajarju’s picture

rajarju commented

Any update on this?
It seems that the form dropdown is not showing the actual value.
Its always showing 1.0

rajarju’s picture

rajarju commented
Status: Active » Needs review
Issue tags: +Needs manual testing
StatusFileSize
new 2045297.patch1.32 KB

Have a patch for this.

kylebrowning’s picture

kylebrowning commented
Version: 7.x-3.4 » 7.x-3.x-dev

tests should be run against dev.

kylebrowning’s picture

kylebrowning commented

#5: 2045297.patch queued for re-testing.

kylebrowning’s picture

kylebrowning commented
Status: Needs review » Closed (fixed)

Committed in dev, thanks.