Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
rleeden
7 months agoNew Contributor
Password autofill on rsc.org.uk
When I try to login using 1password to https://secure.rsc.org.uk/account/login, the login is rejected. When I inspect the password field, I can see the correct and expected password (which works if I...
- 6 months ago
Thanks for following up and sharing those details rleeden. That's very helpful.
I had a hunch something was broken or corrupted in the item structure, so I think this would confirm that. In the other case I've personally seen like this, the item in question had been imported into an older version of 1Password, then changed again with the upgrade to the current version. Apparently something was lost or broken in translation, though in my experience this is very rare and not a foregone conclusion when moving items around between versions or password managers. My apologies again for any hassle here.
I'll go ahead and share this with folks internally so we can keep an eye out for similar cases, and look into replicating. If you run into this again, or if there's anything else we can help with, just let us know. Thanks again!
rleeden
6 months agoNew Contributor
Hi,
Thanks for your reply. To answer your questions:
- I login to the RSC website as follows:
Starting at https://www.rsc.org.uk/, I click on Account, which takes me to https://secure.rsc.org.uk/account/login?ReturnUrl=%2Faccount%2Fupdate
Then I click into the Email field, and unlock 1password if I need to (using the 1password icon in the email box), and then click on the 1password autofill prompt. This fills in the username and password, and submits the form. And fails as described in my original post.
- Doing a search in my vault (using 'rsc' or 'rsc.org.uk') only brings up one entry in my vaults
- I have not noticed this on any other sites. I only use the RSC website very occasionally, so I may have had problems before, but didn't bother to look into it further
- I did import passwords from another password manager, but I'm almost certain I created this account after the import
As suggested, I've created a new RSC login item. This new login works as expected, and I even changed my password on the RSC website, and 1password still works as expected.
So I have a new login item called 'RSC - NEW' which works. But I still have my old login item in 1password - now called 'RSC -OLD'. I manually copied my new password from 'RSC - NEW' to 'RSC OLD', If I now try to login to the website using 'RSC - OLD' I sill this the odd behaviour. It fills in the password field with my new password + space + the very first password I used for this website.
Obviously, I am fine to use my new login item, and I will archive the old one, but something strange was going on. If you need any further info, let me know.
Richard
rleeden
6 months agoNew Contributor
Further to my above message, I looked at the 'RSC - OLD' item via the CLI, and it looks odd! A redacted version (piping the op command through 'cat -v') is:
ID: <REDACTED>
Title: RSC - OLD
Vault: Private (REDACTED)
Created: 3 years ago
Updated: 17 hours ago by Richard
Favorite: false
Version: 9
Category: LOGIN
Fields:
ctl00$ctl00$MainContainer$MainContent$C014$ctl00$ctl00$EmailConfirmation: REDACTED@REDACTED.com
password: [use 'op item get REDACTED --reveal' to reveal]
ctl00$ctl00$MainContainer$MainContent$C014$ctl00$ctl00$PasswordInput: [use 'op item get REDACTED --reveal' to reveal]
ctl00$ctl00$MainContainer$MainContent$C014$ctl00$ctl00$RSCShopSignUp: M-bM-^\M-^S
URLs:
website: https://www.rsc.org.uk/ (primary)So looks like this record has somehow been corrupted.
- 1P_Timothy6 months ago
Community Manager
Thanks for following up and sharing those details rleeden. That's very helpful.
I had a hunch something was broken or corrupted in the item structure, so I think this would confirm that. In the other case I've personally seen like this, the item in question had been imported into an older version of 1Password, then changed again with the upgrade to the current version. Apparently something was lost or broken in translation, though in my experience this is very rare and not a foregone conclusion when moving items around between versions or password managers. My apologies again for any hassle here.
I'll go ahead and share this with folks internally so we can keep an eye out for similar cases, and look into replicating. If you run into this again, or if there's anything else we can help with, just let us know. Thanks again!