AWS console account id being replaced with one-time password
Comments
-
My AWS console login looks like this:
When I autofill with 1password X, it replaces the account ID above with my OTP number:
(I have LastPass installed, but it's not logged in when I use 1Password)
0 -
@yellowbkpk – Thanks so much. I'm not getting the same results on my end. Can you try recreating the Login item? Here's how:
- On the page in your screenshot, copy and paste your account ID, username, and password into the proper fields.
- Click the
Save in 1Passwordoption underneath the password field. - I'd suggest adding the word "new" to the title so you can distinguish it from your existing item. Click Save.
You'll need to sign into your account to grab your QR code to set up TOTP for the new item. Once TOTP has been added, try filling with the new Login and let me know if you see any different results.
0 -
This is happening to me as well... and I have several AWS logins stored w/ MFA tokens, so hoping I won't have to recreate all of them :(
I also know a colleague of mine ran into this problem Friday trying to setup another associate of his with this scheme.
Happy to share any other details if it'd be helpful.
Thanks.0 -
1Password 7
Version 7.4.3 (70403002)
1Password StoreChrome, Safari, Firefox all behave the same.
0 -
Hi everybody - just adding a data point here. This is also happening to me, and the workaround given in this thread has fixed it (I realize that's not a great option for everyone, just adding that it worked).
macOS 10.15.3
1Password 7.4.3 (70403002)
Safari 13.0.5 (15608.5.11), native (non-X, non-beta) extension installed with 1Password app
Chrome 80.0.3987.163, "1Password extension (desktop app required)" 4.7.5.90Hope that aids in diagnosis.
0 -
1.18.0 for Chrome .. same result as this post.
Found that I had Firefox updates off, so fixed that and installed 1PX there... that works for Firefox :)
Safari doesn't appear to have 1PX, just the 1P Extension (7.4.4) but it doesn't seem to be working at all now :(0 -
Chrome Version 80.0.3987.163 now ... 1P Extension disabled ... 1PX 1.18.0 ... still has the issue.
Safari (Version 13.1 (15609.1.20.111.8)) is back to working with 1P Extension, but not for the AWS console still.
... after restarting my mac.0 -
This issue is quite annoying for months.
0 -
@robpark – Thanks for confirming that for us! I'm glad that 1Password X in Firefox is working for you. As a workaround, you can add a custom field with the label of
accountand a value of [your account number].While the fix was pushed with 1Password X 1.18.1, that build is currently in review by the Chrome Web Store. If you're wanting a fix right away, you can install the 1Password X beta in Chrome.
For Safari, that extension is powered by the 1Password for Mac application, which hasn't received the fix yet. However, the workaround I mentioned above should do the trick in the meantime.
0 -
I'm sorry for the trouble, @henry_csft. I'd suggest checking out the workaround I mentioned in my last comment. That should help you out for now. If you have many AWS Logins and the workaround isn't feasible, you're welcome to give 1Password X a try. It's available for Chrome, Firefox, and Chromium-based browsers.
0 -
That workaround didn't work for me in Chrome, but mostly just happy to hear there's a fix on the way.
Thanks!0 -
I know this is a 1PasswordX topic, but I have the same issue with the desktop app + Firefox extension (forum search brought up this as the only even remotely connected forum post).
1Password 7
Version 7.4.3 (70403002)Latest extension
Tried all the tips (the field name was already "account", deleting the entry did not help).
Any chance this will be fixed in the desktop app(+extension)?
0 -
Any word on when this fix will be pushed to the macOS App Store?
0 -
@sagikazarmark & @bilboa – I don't have any updates to share, and the 1Password for Mac team (or any team) doesn't share their release schedule. If you're interested in grabbing 1Password X for Firefox (where the AWS issue is resolved already), you can install it here.
For the workaround in the meantime, you'll want to edit the item, then insert
accountas a label and [your account number] into where you see "new field." Here's what I mean:Before
After
Let me know if you have any trouble after that!
0 -
None of the workarounds worked with 1.18.0, but it just updated 1.18.1 and now is resolved for 1PasswordX.
0 -
Here to confirm that this issue seems to be fixed in the 1.18.1 release, this is awesome!
0 -
@henry_csft and @flyinprogrammer – Yes!! 1Password X 1.18.1 was published in Chrome yesterday I believe. That build included the fix to the AWS issue. I'm so glad the fix made it to you folks now. ❤️
0 -
Any update on fixing this in Safari?
0 -
@jxn – I don't have an update on when the fix is coming to 1Password for Mac. However, the workaround I mentioned in this comment should help you out for now. ❤️
0 -
Please provide an update for a fix for this. It is a constant, daily struggle for my team and myself. Having a workaround is good, but we have so many AWS accounts and separate logins for those accounts it's not practical for us to hand edit them all to include a dummy field to correct this issue.
0 -
Thanks for the bump, @wagnerone! The filling algorithm was recently updated in the 1Password for Mac beta. I don't have a timeline for when it'll be released to the stable version, but you're welcome to use the 1Password for Mac beta or 1Password X for the time being.
0 -
This workaround: https://discussions.agilebits.com/discussion/comment/554939/#Comment_554939 indeed works, but months later on Mac Chrome and 1pass extension 4.7.5.90 this is still an issue :(
0 -
The latest macOS client beta has fixed this issue! I confirmed it by logging into like 10 AWS accounts. It was glorious.
0 -
Thank you for the update! I am glad to hear this :)
0 -
I have version 4.7.5.90 of the extension (not 1PX) and it's still an issue.
0
