6 ms·
Questions: 1. If you are using this to authenticate a non-Google service, can Google cut off your access to that service? 2. If your Google account is termina
by Animats 4y ago
Questions:
1. If you are using this to authenticate a non-Google service, can Google cut off your access to that service?
2. If your Google account is terminated, do you still have access to non-Google services?
3. Does Google possess sufficient information to log into non-Google services as you?
4. In the event that any of the above happen, do you still have the right to sue Google?
- prepend 4y agoThis is just for authenticating to google, right?
- Nifty3929 4y agoYes, but if you use the “Login with Google” function on many 3rd party websites, then what? If Google locks you out, can you get back into your account on the 3rd party website? I think this is a great question, and that the answer depends on the 3rd party site.
- theaiquestion 4y ago> Yes, but if you use the “Login with Google” function on many 3rd party websites, then what? AFAIK this part has nothing to do with passkey's and is an issue with OAUTH, and has been an issue for years.
- tisc 4y ago> […] and is an issue with OAUTH This issue is not caused by OAuth, but by offering authentication via a third party. If you allow visitors to authenticate via a third party, you implicitly trust that third party. If that third party decides to revoke your account, then the logical consequence is that you can no longer authenticate. There’s no solution for this problem imo, other than not allowing authentication via a third party. It is the same as airlines; They want you to identify using a passport. If your country decides to revoke your passport, you cannot check-in. That’s not an issue, but a logical consequence of choices made.
- Animats 4y agoThe trouble is that you can, apparently, have only one trusted third party. You can't have a backup authentication service in case the trusted third party fails. That's what's needed. I'd like to have a regulated entity such as a bank, or even the California DMV, as a backup authentication provider. They have legal obligations that Google does not.
- judge2020 4y agoYou'd need a law saying that the California DMV or whoever must run an oauth service, and then you'd see people integrate it. As it stands, this isn't a thing because the California DMV and even banks aren't interested in being the populus' IDP.
- Animats 4y agoBanks are into this. JP Morgan Chase uses OAuth2 for some services. It's more of an enterprise thing right now.[1] [1] https://www.jpmorgan.com/technology/technology-blog/protecting-web-applications-via-envoy-oauth2-filter https://www.jpmorgan.com/technology/technology-blog/protecti...
- trallnag 4y agoYep. I think Google is once again trying to place itself as a gatekeeper. The vast majority of apps out there will never implement passkeys.
- notatoad 4y agothere's two things here, passkeys as a mechansim to sign into your google account, and passkeys in general. i'll assume you're asking about passkeys in general, even though the announcement here is passkeys to sign into your google account - passkeys as a general standard were introduced earlier this year. 1. no, it's a cryptographic key stored on your device. but also yes, because if you're using a passkey on a device you sign into using your google account, google can lock you out of that account and potentially that device. if that device is your only way of logging into a service, you'd be locked out of the service in the same way that losing or destroying the device would lock you out of the service. but authorizing multiple passkeys and adding backup authentication methods is encouraged, so for practical purposes the answer is no. 2. you should understand that passkeys are issued by your device or browser. so if you don't want to trust google, you can use a passkey issued by safari or iPhone instead of Chrome or Android. if you're using an apple-issued passkey to sign into some other service that isn't your google account, google has literally no involvement anywhere in that chain. 3. not according to the spec. the passkey is a certificate that gets stored on your device. your device shares a signature (not the certificate) with the service you're signing into to prove you have access to the certificate. but they're issuing you the cert through their proprietary software. if you don't trust google to not snag a copy of the passkey when they generate it for you, you should use passkeys generated by an issuer that you do trust. (in apple's implementations, passkeys are synced through iCloud, so the answer there is yes - apple does have your passkeys and could sign in to services as you if they wanted. google is not doing that.) 4. you'd have to read the ToS for yourself to figure out what you could sue google for. but the more relevant thing than legal recourse is that this scheme doesn't really give google any power they don't already have, and in many ways distributes power out to third-parties so you have to trust google less. apple's passkey implementation is leading google's. others will follow. this is about allowing you to use an open standard to authenticate with your google account.
- devsda 4y agoOn point 1 if google decides to lock you out of its service, it generally doesn't stop at a single device but all other devices you own and associated accounts can also be impacted. So, the solution here seems to be not just creating backup devices (using the same account) but diversify the platforms as well like use a mix of android, yubikey, ios and any other supported platforms. Doubt many people would have the time and resources to do it correctly.