4 ms·
When you use Google or FB or others to sign in, you just get some data, that you can trust. Internally, on my website, i may have an account, that i then link
by okr 6y ago
When you use Google or FB or others to sign in, you just get some data, that you can trust.
Internally, on my website, i may have an account, that i then link to this Google or FB account.
1) If Google shuts down an account, authorization might still work for the purpose of logging in somewhere else. Your email might not work anymore, like any other services within Google. But authorization does. That it does not, is an implementation detail.
2) Since internally i have created an account, that is only linked to your Google account, i can always allow you to also login via any other method. Maybe with your facebook account.
3) I think, things will become better. You use your devices to authorize yourself. And i then trust your device. Then there is no 3rd party involved anymore.
- antonfire 6y agoRegarding point 3, the trend is in the direction of making your devices a lot less "yours", and a lot more hooked into 3rd (4th, etc) party services.
- okr 6y agoMany people use yubikeys, for example. As a user, i declare ownership over these keys. I buy these. They become mine. And i use them then for authorization. So it is a mix, i would argue. For machines it is just important to identify you. And in the past, so i have read the users, they all want to get away from password authorization. Just make the darn thing recognize me. (and sometimes not)