10 ms·
As they point out at the very bottom, all their arguments apply to all third-party sign-ons, so they're removing Facebook as well. So there's nothing specifica
by crazygringo 6y ago
As they point out at the very bottom, all their arguments apply to all third-party sign-ons, so they're removing Facebook as well.
So there's nothing specifically against Apple, despite the title seeming to imply it -- just that they're taking the move right now because of Apple's new policy coming into effect.
I've got to say, I really wish there were a way to know whether I already used Facebook, Google, or Apple to log into a site or app before. My password manager is usually pretty good at letting me know if I've got a "normal" account with user/password, but it doesn't do anything to remind me if I ought to log in with one of the other services.
Every time I'm occasionally asked to sign into Spotify, Pinterest, Medium, Quora, etc. -- it's like, I'm pretty sure I've signed up with something before, but who even knows which one, or multiple?
If password managers could start saving that you've got accounts associated with Apple/Facebook/Google and highlight the relevant button on sign-in, it would be a big feature improvement.
- TheSpiceIsLife 6y agoThis happened to me recently where, in a hurry and distracted, I logged in with one or another third party auth service then realised that wasn’t the correct login as it displayed a new account.
- jborichevskiy 6y agoYes! Especially once you start juggling multiple accounts for different companies and projects. Becomes a guessing game, and each wrong guess creates another account magically. Infuriating
- warent 6y agoTime to create a new service to unify all your SSO accounts! One single SSO!
- NorwegianDude 6y agoIf only there was a decentralized option that has already solved this... We could call it OpenID or something like that... Oh, wait..
- rapnie 6y agoYou also have IndieAuth that is slowly gaining more adoption. https://en.wikipedia.org/wiki/IndieAuth https://en.wikipedia.org/wiki/IndieAuth https://indieauth.net/ https://indieauth.net/
- NorwegianDude 6y agoCool, that looks awesome, thanks!
- jmull 6y agoHere comes SSSO! I can hardly wait! Of course, there may be competing SSSO solutions...
- toyg 6y agoWe could have a Simplified Experience Single-Sign-On, or SESSO. Italian developers would adopt it enthusiastically.
- core-questions 6y agoYes! and then I just sign in once into my single SSO signon!
- admax88q 6y agoOpenID would have done it, but Facebook and Google neutered it in favour of OAuth so they could cement themselves as primary players.
- tannhaeuser 6y agoIt's been some time last I checked, but isn't OpenID Connect provided anymore by Goog/Fb? Why wouldn't that be a reasonable choice if you wanted a protocol that, from the dev side of things, allowed you to uniformly target external auth providers, or your own?
- admax88q 6y agoOoenID Connect is different. Its basically just OAuth2, and google/fb require the ap developer to register their app with google/fb in order to authenticate users. Whcih is pretty bad for both developers and users, as a user I cant run my own identity provided and as a developer I have to spend time setting up accounts with ever identity provider i wish to integrate. Original OpenID just let me as a user use a URL as my identity, so I could use any identity provider I wanted, including running one myself. EDIT: There is a specification for dynamic client registration but nobody implements it as far as I've been able to tell.
- dmitshur 6y agoAnd if you create an account accidentally, there’s often no way to undo that. Next, if you don’t add a second-factor with to it, it becomes a ticking countdown until the account is compromised.
- joshspankit 6y agoHaving had this same problem multiple times, I actually made it a point to save a “login” for those sites that when I autofill it reminds me which auth service I’ve used. Username: Log in with FB Password: <blank>
- niyikiza 6y agoNeat trick. Some websites don't even bother giving you any choice for traditional username/password input though.
- jdironman 6y agoIt's just a further example of the software / online experience being so...fluctuating as a whole. Which has its pros and cons. Pros being freedom of visual and interactive expression. Cons being lack of expectation.
- JAlexoid 6y agoSome places require no additional info from you. There are good use cases where third party logins are good enough.
- joshspankit 6y agoIn that case, I just click the icon for my pw manager (1Password in this case), and the modal shows me the same message.
- efreak 6y agoMy router doesn't accept a username at all, which actually makes a bit of sense since there's only one 'account' on it. Unfortunately, this means that neither the browser nor LastPass will save the password. My previous router allowed me to change both the username and the password, then pre-populated the username field with whatever I'd entered (but didn't disable the field), which I always thought was odd...
- ben509 6y agoI do something similar with a generic password manager. I've tried pinging the developers to support the idea directly, but I've been met with incomprehension. Not sure if I'm explaining it wrong, or if it's way more work than I'm anticipating.
- thaumasiotes 6y ago> As they point out at the very bottom, all their arguments apply to all third-party sign-ons, so they're removing Facebook as well. That section of the post was surprising. If they're not supporting Sign in with Apple, then obviously they're going to remove support for all other third-party sign-ons, because those third-party sign-ons are what trigger the obligation to support Sign in with Apple. Ending their post about "why we won't be supporting Sign in with Apple" with a note that they're also ending Sign in with Facebook on the merits of third-party sign-in is quite disingenuous. It doesn't matter at all what they think about the merits of Sign in with Facebook; those thoughts are completely irrelevant to their decision.
- mdavidn 6y agoI cope with this confusion by avoiding third-party login whenever possible. Why volunteer additional information about myself to Google or Facebook?
- sequoia 6y agoBecause you can frequently avoid account creation, setting a new password etc if you click “sign in with google.” It’s a tradeoff but if you don’t see any value in it you maybe haven’t used it- it’s convenient.
- fladrif 6y agoWith a password manager though, I avoid having tradeoffs in the first place. I get some amount of anonymity by separating my accounts, and it's trivial to login to sites with the same amount of clicks as with third party sso.
- rtpg 6y agoPassword manager doesn't stop you from having to fill in a bunch of stuff. Like yeah, it's only a couple minutes, but if it's for an app you'll use a handful of times in your life, just hitting that G will be much nicer.
- bpicolo 6y agoMost of them have a hotkey for fill out + submit form.
- fomine3 6y agoRegistering a new site on PC browser with password manager is fine but on mobile with password manager is bother. It won't register new ID/password automatically.
- andrewaylett 6y agoChrome on Android is persistently annoying about wanting to save new IDs, and will also try to save logins for apps. That gets turned off fairly quickly, as I use Bitwarden, which _also_ prompts to add new accounts when I sign up or log in. It's not foolproof, but given I'm generating the password in Bitwarden anyway, it's not the end of the world if it doesn't catch it.
- ourcat 6y ago> "I really wish there were a way to know whether I already used Facebook, Google, or Apple to log into a site or app before" You can. On each of the places you mention (Google and Facebook, certainly), somewhere in a settings page/window, you'll find your list of 'authorised apps'. These will be a list the login systems to the third-party sites you've used to log in with. You should then see a way to 'revoke' their access to your data.
- jdxcode 6y agoThat doesn't solve the problem. You would have to go to every method to figure out which one it might be listed under. It needs to be in the browser/password manager to tell you which service was used.
- rahimnathwani 6y ago"all their arguments apply to all third-party sign-ons" No they don't. Other sign-on options don't obfuscate the email address. They are likely removing FB login as otherwise their next app update will be rejected by Apple for supporting third party login but not Apple login.
- monadic2 6y agoSurely you can’t hide your email from apple itself.
- saagarjha 6y agoYou can't; the design behind Sign in with Apple is that you've already trusted them with your email as you're using it to buy apps from the App Store.
- monadic2 6y agoTrusting them to protect your arbitrary data is a completely different scenario; there’s just more concentrated risk (i.e. your identity is just gone when Apple gets taken).
- scarlac 6y agoIt used to be true that during a Facebook Connect session the user was asked if they wanted to share their email or not. I faintly remember you could even choose a proxy fb e-mail aka "fake email". Did they remove that feature?
- necovek 6y agoA party in OAuth authentication can request some obligatory information, and if email is part of it, you won't be able to deselect it. In general, sites use email as an indication of a unique, real person. I imagine most of them do not really care about it afterwards, which is why the SSO systems even work (though, they can demand an email too).
- cbhl 6y ago> I've got to say, I really wish there were a way to know whether I already used Facebook, Google, or Apple to log into a site or app before. Bookwalker (from Japan) draws a big red box around the login you used last on a given device. Presumably they store a cookie/sharedpreferences with it. It doesn't look pretty, but it helps.
- saagarjha 6y agoThat's useful, but on any device of mine I'm usually logged in anyways. What would be really useful is knowing this when I log into a new computer.
- grawprog 6y ago>My password manager is usually pretty good at letting me know if I've got a "normal" account with user/password, but it doesn't do anything to remind me if I ought to log in with one of the other services. Doesn't it somewhat defeat the purpose of using a password manager if you use one account to sign into multiple sites? Sign on services from main accounts seem like security flaws. If you use one main account resonsible for all your 'main things' to sign in to all the 'other things' that gives one vector of attack to enter or compromise 'all the things'. Password managers exist to make the management of many things as easy as one thing, not to adapt to using one thing for everything, that's pretty much the opposite of what a password manager does. Sign on services don't exist for convenience, despite being marketed that way, they exist to increase data collection abilities. Password managers exist to make using multiple accounts as easy as using a sign on service, that's the point. They should be separate from existing providers. They are an alternative to them.
- thaumasiotes 6y ago> Doesn't it somewhat defeat the purpose of using a password manager if you use one account to sign into multiple sites? Yes. Password managers exist to solve the problem of credential reuse; third-party login exists to implement credential reuse. They are fundamentally opposed.
- fennecfoxen 6y agoThe credentials are at least not in multiple databases and stand some chance of being more secure, so it’s not as bad as with direct credential reuse, but yes, if you do compromise that one identity provider you’re in big trouble.
- jacurtis 6y agoWith Social SSO, you essentially are passing the trust from some random company getting hacked and revealing your re-used password, onto the shoulders of internet giants like Facebook, Google, Twitter, Apple, etc and putting the trust on them, that they know what they are doing in terms of security. I still agree that they are variants of the same fundamental problem (a single credential protects all of your logins) and that Password Managers are a vastly superior solution to this problem. But it is worth pointing out that for the layman, using Sign in With Facebook/Apple/Google, is better than single credential re-use. When I say "layman", I mean people like my mom and grandma. I have tried to get my mom to use a password manager (went as far as to set it up for her, and pay for it) but she just reverts to a simpler solution (which is Social SSO). If she weren't using Social SSO, she would be using her same Facebook password for every site on the internet. So as much as I personally loathe Facebook, I do trust Facebook for securing my Mom's credentials far more than the random scrapbooking website she is creating an account for. In this case, I am grateful that she is using Sign In With Facebook, even though I would never consider such an action for myself. So it is a small step in the right direction.
- jasonlingx 6y ago> As they point out at the very bottom, all their arguments apply to all third-party sign-ons, so they're removing Facebook as well. Nope, not all their arguments. Only some.
- cj 6y ago> So there's nothing specifically against Apple The one thing that is specifically against Apple is the new App Store policy that if an app uses google/Facebook sign in, the app _must_ also use Apple Sign In.
- habosa 6y agoI worked on a product that can do that (Google Smartlock for Passwords) but these “identity provider” hints were extremely confusing to both users and developers. The UX definitely could have been better but overall I just don’t think it works.
- Thorrez 6y ago> all their arguments apply to all third-party sign-ons What about the argument that users check their gmail addresses regularly but rarely check their icloud email addresses?
- imron 6y ago> So there's nothing specifically against Apple, despite the title seeming to imply it From the article... > In addition to these customer experience problems that are common to all third-party login systems, Sign in with Apple introduces several more that are unique to it.
- ryanianian 6y agoI create dummy logins in my password manager for sites that use external auth. Username of just “LOGIN WITH GOOGLE”. Hacky but it makes me smile every time it gets filled in.
- kripy 6y agoPerform an audit on yourself. Both Facebook [1] and Google [2] have pages where you can check third-party apps that you have connected with. You might be surprised what you find. [1] https://www.facebook.com/settings?tab=applications&ref=settings https://www.facebook.com/settings?tab=applications&ref=setti... [2] https://myaccount.google.com/security https://myaccount.google.com/security
- deleted 6y ago[deleted]
- mcintyre1994 6y ago> As they point out at the very bottom, all their arguments apply to all third-party sign-ons, so they're removing Facebook as well. Nope, some of them also apply to Facebook, and Facebook has the additional destruction of privacy concern. They have to remove Facebook or support Apple too because of the policy and have chose neither instead of both. Some of their concerns specifically don’t apply to Facebook/Google/anything directly tied to your real email that you’d otherwise choose to sign up with. You add a bit of complexity to your database to record different login types, but you can easily reconcile them to an existing user if the emails match, and provide the features they want like searching for a user by email.
- spullara 6y agoThis is as close as we got trying to do it from the app itself: https://www.lukew.com/ff/entry.asp?1906 https://www.lukew.com/ff/entry.asp?1906 I absolutely agree that password managers could remember this stuff. Single-signon is pretty easy to identify and you could setup the relationship.
- ivoecpereira 6y agoAs I would liked your approach in other times, wouldn't it be a bad one in today"s privacy matters/GDPR and being able to enumerate your database?
- deleted 6y ago[deleted]
- envolt 6y agoNot all. 1. Apple obfuscate email - this complicates the support system, and as per them Apple hadn't thought about it thoroughly. Collaboration is obstructed. Password recovery is not an easy process. 2. Cross Platform - The post states that Apple vaguely says that sign in on Android is possible, but doesn't state how it is to be done.
- yreg 6y ago>Apple vaguely says that sign in on Android is possible, but doesn't state how it is to be done. They do? https://developer.apple.com/documentation/sign_in_with_apple/sign_in_with_apple_js/incorporating_sign_in_with_apple_into_other_platforms https://developer.apple.com/documentation/sign_in_with_apple...
- meerita 6y agoI don't support social login anymore. It's better for the customer.
- dalore 6y agoPaperspace has this with their Google integration. And I've implemented this pattern before in web dev. You return to the site and if you have logged in with social media site before, and it detected you are still logged in, it will auto login for you.
- neya 6y agoDid you actually bother to read the post? The post specifically explains the headaches associated with Apple sign in. In particular - "Another issue is Sign in with Apple’s “Hide My Email” feature. With this feature, if you create an account with us, Apple will generate a special email address just for that account. So rather than your email address being john.doe@icloud.com, we will see your email address as something like dpdcnf87nu@privaterelay.appleid.com. While this is an intriguing idea that provides a measure of privacy, in practice it creates numerous support and user experience headaches..."
- dustinmoris 6y agoTBF if single sign on is implemented correctly and you use the same email address across your accounts then it shouldn't matter which SSO you're using. When you log in for the first time it should request permission to "see your email address". Then you authenticate with your provider and get redirected back at which point the website should create an account for you on behalf of that email address. If next time you log in again via a complete different provider which has the same email address then it should just work. I mean that is the whole point of this...