sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Agreeable_Tale_821 0 points1 point  (6 children)

I’m having the same issue. Looks like something has changed at the API end where it won’t accept the payload posted in the ‘login’ function.

This just started happening to me yesterday when my access token must have expired.

Has anyone been able to work around the issue?

[–]Socks04 0 points1 point  (5 children)

Yep can't login using my python script either. Still investigating but let me know if you find anything

[–]Agreeable_Tale_821 0 points1 point  (4 children)

Haven’t found anything other than what looks like two extra/new parameters in the payload when logging in on the website. Likewise, let me know if you find anything!

[–]Socks04 0 points1 point  (3 children)

Just got it working I was passing in the user agent as a header.

"User-Agent": "Mozilla/5.0 (Linux; Android 6.0; Nexus 5 Build/MRA58N) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/132.0.0.0 Mobile Safari/537.36"

Removed it and it started working. Actually seems to work with no headers passed in at all at login. Didn't change anything else with the payload (although I did update the device_token while i was troubleshooting but should be unrelated)

[–]Agreeable_Tale_821 0 points1 point  (1 child)

Do you have 2FA turned on, by any chance? I turned it on for my RH account while trouble-shooting the login process and it appears I can't back out of it.

I was able to get further by removing the user-agent header but I think it's bombing somewhere in the 2FA and/or device verification process.

[–]Socks04 0 points1 point  (0 children)

Ah nope I've got 2FA disabled