404: Page Not Found on "Visit our sign-up page..."
With Testflight installed and 1Password appearing in it and then clicking the link "Visit our sign-up page..." in the Beta Invite email (in iOS Gmail app), I a get 404: Page Not Found on the 1Password website.
1Password Version: 8.10.9 (81009045)
Extension Version: Not Provided
OS Version: iOS 16.5.1 (c)
Browser: Gmail app
Comments
-
Same here
0 -
Same as well
0 -
Same
0 -
Same for me!
0 -
Looks like this happens when the beta app is not yet installed. The link opens in the app and if it’s not installed you see the 404 error as the old app doesn’t open.
0 -
Ah! When I sign up, should I use my current account address or do i need to use a brand new email address?
0 -
Hi folks,
A few notes here:
We're aware the page doesn't have any content (404) if you don't have the beta installed. That is expected at this point. As we move through the beta period we'll be looking to get some sort of placeholder up there, but the idea is that the link should be opening in 1Password, not your web browser.
tl;dr: What butterford said.It may work best to try tapping the link from the Mail app on iOS, rather than an app such as Gmail which intercepts links you tap. This is an unconfirmed theory at this point. If you're having this difficulty and have installed the beta 1Password app from TestFlight, and you're using something other than Mail, I'd appreciate it if you could please try using Mail and see if that works better.
When I sign up, should I use my current account address or do i need to use a brand new email address?
A separate email address would be the best approach.
"When you’re asked to enter an email address, use an email address that isn’t tied to an existing 1Password account." from Unlock 1Password with a passkey (private beta)
Thanks for this batch of initial feedback, folks! If you've been having trouble please let me know if the above helps.
Ben
2 -
Open it on your device with 1Password installed - it will take you to account setup
0 -
Ben, et al, my issue was not related to Butterfield's "no beta ver installed". It was installed.
I got this to work, not by using iOS Mail, but but taking the link above
https://support.1password.com/cs/passkeys/#step-1-create-a-new-account-with-a-passkeyand opening it with iOS Safari (I normally use iOS Chrome). This opened correctly in iOS 1Password at the "Set up your account" dialogue. I was able to successfully create a new account with a different email address and save a passkey. I created a secure note as a test.
For fun, I went to my MacBook, with 1Password for Mac 8.10.9 (81009045) and went to Manage Accounts, and was able to login to my new account by authenticating from my phone and making the MacBook a trusted device. Nice!
I saw that the new passkey was stored in my iOS Passwords. I then went to Safari on MacOS and tried to login with my new account at my.1Password.com and as expected, it wanted to unlock with a passkey. When I told it to, it popped up a dialog with a 6 char code? I canceled, and found the 1Password app open. But in Safari, it showed "Unable to sign in with passkey". After quitting 1Password and trying again, it fails to open with a passkey and 1P doesn't open. Maybe the beta isn't this far along yet?
What I don't understand is whether the new account/vault is protected by a Secret Key? Is my main/original 1Password account the "parent" of this new account?
0 -
Thanks @Mike Molloy. We have heard similar reports about Chrome, and I suspect the same thing is happening if clicking the link within the Gmail app. 🤔 We're working to confirm the same on our end and then update documentation accordingly.
For fun, I went to my MacBook, with 1Password for Mac 8.10.9 (81009045) and went to Manage Accounts, and was able to login to my new account by authenticating from my phone and making the MacBook a trusted device. Nice!
🎉
I saw that the new passkey was stored in my iOS Passwords. I then went to Safari on MacOS and tried to login with my new account at my.1Password.com and as expected, it wanted to unlock with a passkey. When I told it to, it popped up a dialog with a 6 char code? I canceled, and found the 1Password app open. But in Safari, it showed "Unable to sign in with passkey". After quitting 1Password and trying again, it fails to open with a passkey and 1P doesn't open. Maybe the beta isn't this far along yet?
I'm checking into this for you. 👀
What I don't understand is whether the new account/vault is protected by a Secret Key? Is my main/original 1Password account the "parent" of this new account?
There isn't any relationship between the accounts, and accounts with passkey unlock enabled do not have an account password or Secret Key.
I hope that helps!
Ben
0 -
I saw that the new passkey was stored in my iOS Passwords. I then went to Safari on MacOS and tried to login with my new account at my.1Password.com and as expected, it wanted to unlock with a passkey. When I told it to, it popped up a dialog with a 6 char code? I canceled, and found the 1Password app open. But in Safari, it showed "Unable to sign in with passkey". After quitting 1Password and trying again, it fails to open with a passkey and 1P doesn't open. Maybe the beta isn't this far along yet?
It sounds like this is part of the expected workflow. You'd obtain that code from the 1Password app on your iPhone and enter it into Safari. This is part of the new device authorization process.
Ben
0 -
@Ben, can you explain the relative security of a vault/account secured only by a passkey as opposed to using a Secret Key and password?
0 -
@Mike Molloy We are using our trusted device security model to maintain E2E encryption even though there is no password or secret key for a passkey account. In this security model the passkey is only doing identity verification with 1Password.com and not protecting the data directly.
We have published a blog post on how the trusted device model works in the context of single sign-on. All the security properties described there apply to our unlock with passkey accounts
0
