Can't log in (incorrect password)

[NotGus]

So I can't remember my password and I was somehow logged out. But, I have my little number that I used to join a group. Can I use that to log back on? I really want to continue using habitrpg.

[lefnire]

on it now

[ianoff]

Related: I can log in to the derby version at old.habitrpg.com, no problem, but not the rewrite:

Exact same UN / pass, same case on username (lower). I use 1Password, if that helps; do you think the autofill of the password field is messing it up?

Edit: yeah, that was it: password managers like 1Password apparently mess up the login process on the Angular rewrite only. Weird.

[lefnire]

If you get a chance Meagan, can you peak at the code for the old / new mismatch? I gotta jump back to work, but will dive in again tonight.

In the mean time, I added PW-reset, and then after you're in PW-change (to put back to your normal PW):

[ianoff]

I got in, just had to do the PW by hand and not use 1Pass and it was fine.

here's a peek: 1Pass is trying to fill in both the login and registration (see the faded back box on the left) and there's a message in the console: POST https://www.habitrpg.com/api/v1/user/auth/local 401 (Unauthorized)

[lefnire]

there's definitely a 1pass ticket floating around, i'll need to find it and reference when i hit this next. The gist was 1pass was incompatible with how derby forms with x-bind=submit.. handled things. Had a conversation over on 1pass forum (linked said ticket) about how to mitigate that once we're off Derby, so we'll just need to work those suggestions into our angular forms. In the mean time, let's have people blacklist habit for 1pass for now

Edit: might just be we need to add action='POST' to all forms, even if they have an ng-submit

[lefnire]

#1246 is the issue i was referencing. I just added an action='POST' to the form, can you see if that solved the issue?

i'm marking this ticket down in prio, after some to-and-fro in the issue queue, I realized many of the login issues weren't login issues at all, but API errors for derby-corrupted user data. This one in particular simply looks like the same issue as #1246 , which black-listing Habit for LastPass or 1Pass is the temporary solution till we can get around to this

[paglias]

I think we can continue on #1246 since they seem exactly the same issue related to 1pass