Can't get amazon.com login to work

Jim_here

I followed this procedure to create a new login for amazon:
Sign in to websites with username and password split across multiple pages

The first signin page has a humongous url, which in my case, was:
https://www.amazon.com/ap/signin?openid.pape.max_auth_age=0&openid.return_to=https://www.amazon.com/?ref_=nav_ya_signin&openid.identity=http://specs.openid.net/auth/2.0/identifier_select&openid.assoc_handle=usflex&openid.mode=checkid_setup&openid.claimed_id=http://specs.openid.net/auth/2.0/identifier_select&openid.ns=http://specs.openid.net/auth/2.0&

In the saved login, it got shortened to
https://www.amazon.com/ap/signin

Which is fine, except it doesn't work - brings up "Looking for Something? We're sorry. The Web address you entered is not a functioning page on our site".

Should I replace the short url with the long one in the login? I'm afraid it might not always work because the url could vary.

Using Firefox

---

1Password Version: 7.4.1
Extension Version: 4.7.5.90
OS Version: macOS 10.13
Sync Type: Dropbox

ag_ana

Hi @Jim_here!

Can you please try using just "https://amazon.com" as your 1Password URL?

Jim_here

That goes to the home page. If I navigate to the sign-in page, I can fill it with the url set that way. However, I also have a login for my wife's account. It has the long URL, and gets applied automatically over mine if I just do Command-/ on the sign-in page.

Maybe I just go to the sign-in page fresh and copy that long url into the 1P login?

ag_yaron

Hey @Jim_here ,
Yes, saving the long URL will allow you to also open and fill from 1Password directly. If you save only "amazon.com", then open and fill will take you to the homepage and will not autofill anything.

Give the long URL a try and see how it goes :)

Jim_here

Thanks, yes, that works. With many of those long ones you can truncate it and it still works, but not this one.

ag_yaron

That's correct, @Jim_here .
Amazon will direct you to a broken link page if you try to shorten that URL. Hopefully they will change this behavior in the future :)

I'm glad you got things working properly now though!