News for hackers. Stuff that matters.
Re:Face ID and Touch ID for the Web by yegle on Monday October 19, 2020 @03:58PM (#24830280)
"Sign in with Apple" requires a developer account with Apple.

Having saw Epic's developer account terminated by Apple, I would definitely stay away from any "Sign in with Apple".

(FWIW, the only 2fa with "Sign in with Apple", if you don't own any Apple hardware, is SMS.)

Re:Face ID and Touch ID for the Web by snowwrestler on Monday October 19, 2020 @05:44PM (#24831379)
It's pretty clear Epic set out to intentionally get their Apple developer account terminated so they would have standing to sue, so I would not draw too much inference from that.

That said, it's generally true that any dependence on a platform is a form of risk. There are documented examples of Google kicking people out of their ecosystem unexpectedly too.

Federated sign-in schemes may be a good idea if they help your users create accounts and authenticate more easily, but it certainly seems smart to offer more than one, including your own email-based option.

Re:Face ID and Touch ID for the Web by jeroenhd on Tuesday October 20, 2020 @07:24AM (#24836117)
> It's pretty clear Epic set out to intentionally get their Apple developer account terminated so they would have standing to sue, so I would not draw too much inference from that.

Actually, it's clear that they intentionally got their _app removed_. The termination of their entire Apple account was a step I wouldn't have expected Apple to take because it underlines the fragility of their authentication system. Now, player who signed up to Fortnite on their phones can't continue to play anywhere else, probably making them regret using the Apple sign-in in the first place.

I generally consider any federated login that doesn't have an external email address attached to be fleeting, possibly disappearing out of the blue. I've lost some minor accounts when I deleted my Facebook account with services that didn't offer an email alternative. Developers, at least make adding an email/username and password optional once I've signed in with another service account, because that account might just disappear altogether one day!

Re:Face ID and Touch ID for the Web by ascagnel_ on Tuesday October 20, 2020 @09:48AM (#24837231)
> Actually, it's clear that they intentionally got their _app removed_. The termination of their entire Apple account was a step I wouldn't have expected Apple to take because it underlines the fragility of their authentication system. Now, player who signed up to Fortnite on their phones can't continue to play anywhere else, probably making them regret using the Apple sign-in in the first place.

- Apple never indicated that they’d remove Epic’s SIWA support, and there have been reports that Apple went out of their way to make sure the support would survive the account being terminated [0]

- Apple’s developer agreement allows them to terminate the account of an offending developer after 30 days; Epic’s account was terminated 45+ days after breach.

[0] https://daringfireball.net/linked/2020/09/29/epic-games-unre... (with the caveat that John Gruber shills for Apple, but also has some good contacts within)

Re:Face ID and Touch ID for the Web by athms on Tuesday October 20, 2020 @10:05AM (#24837408)
>John Gruber shills for Apple...

A shill is a person who pretends to give a neutral endorsement but has an interest in the deal.

Re:Face ID and Touch ID for the Web by machello13 on Wednesday October 21, 2020 @03:28PM (#24851163)
Do you think, honestly, that anyone who isn't as critical as you'd like is a shill?
Re:Face ID and Touch ID for the Web by kyriakos on Monday October 19, 2020 @11:10PM (#24833597)
What if I'm running a site that is against apple's beliefs? E.g you run an adult site? Would you risk it?
Re:Face ID and Touch ID for the Web by Cthulhu_ on Tuesday October 20, 2020 @04:07AM (#24834934)
Loads of companies - especially financial processors - don't want anything to do with adult sites, so if you're in that industry you're already up for a challenge.

I've worked for a project for the tobacco industry, similar story.

Re:Face ID and Touch ID for the Web by snowwrestler on Monday October 19, 2020 @11:51PM (#24833781)
Apple doesn't allow adult content in their App Store, but they don't do anything to prevent adult sites from loading in Safari, even on iOS--never have. They seem to draw a distinction between their walled gardens and the open web. I'll admit I'm not an expert on Face ID and Touch ID for the web, but to me it looks like a feature of the Safari browser, not a walled garden.
Re:Face ID and Touch ID for the Web by samtheprogram on Tuesday October 20, 2020 @03:52AM (#24834862)
On the contrary, although not against all uses within Safari, there are rules against use of Sign In with Apple depending on what you are doing, including one against pornographic websites as mentioned.

https://developer.apple.com/sign-in-with-apple/usage-guideli...

Re:Face ID and Touch ID for the Web by brabel on Tuesday October 20, 2020 @03:00AM (#24834584)
They use Web Authn, which is an open Web API : https://developer.mozilla.org/en-US/docs/Web/API/Web_Authent...

Implementing a client with this also works on Android and any computer that supports some kind of hardware authentication mechanism, like fingerprint or face recognition.

Re:Face ID and Touch ID for the Web by ROARosen on Monday October 19, 2020 @09:49PM (#24833235)
>It's pretty clear Epic set out to intentionally get their Apple developer account terminated so they would have standing to sue, so I would not draw too much inference from that.

Nevertheless, the suspension still clearly highlights the fealty you are expected to give to Apple being a dev on their platform, or else.

Re:Face ID and Touch ID for the Web by tomc1985 on Monday October 19, 2020 @10:39PM (#24833458)
And neither is Epic the first nor last of the kind of people who want to pick this fight with Apple, even if they can't
Re:Face ID and Touch ID for the Web by arcticbull on Monday October 19, 2020 @08:54PM (#24832910)
Apple isn't perfect, and yeah, you might run into a situation where you have to sue. Them taking away the ability for half your users two sign in to your app while your dispute makes its way through the courts is seriously problematic.
Re:Face ID and Touch ID for the Web by jen729w on Monday October 19, 2020 @09:08PM (#24833017)
I don’t think it’s ever been shown that Apple did this at all, let alone maliciously.

If anyone has a source to the contrary, we need it here please. And I mean a documented source, not hearsay.

Edit: there’s discussion below.

Re:Face ID and Touch ID for the Web by ogre_codes on Monday October 19, 2020 @04:35PM (#24830711)
As a user I would prefer no account in most cases. As a distant second, I would prefer the convenience, security, and privacy of Sign in with Apple over Google, Facebook, or the headache of managing yet another web account.

As a developer, I use my preferences as a user to steer my choices, but recognize that the world doesn't revolve around Apple so would allow other options.

> Having saw Epic's developer account t...

Since I have zero need to deliberately violate Apple's App Story policy, I don't worry about this overmuch.

Re:Face ID and Touch ID for the Web by simonw on Monday October 19, 2020 @04:51PM (#24830874)
> Since I have zero need to deliberately violate Apple's App Story policy, I don't worry about this overmuch.

That may be true today, but their policies are a moving target. Who knows what they'll be like in a year's time?

Re:Face ID and Touch ID for the Web by ogre_codes on Monday October 19, 2020 @05:44PM (#24831373)
> That may be true today, but their policies are a moving target. Who knows what they'll be like in a year's time?

Likewise Google, Facebook, or any site/ API that a developer deals with on a daily basis.

I wouldn’t bet my company on any sign in with _____ service. I just feel the trade-offs with Apple’s sign in versus Google/ Facebook to be less bad. With any of the services, I might do something that causes me issues down the road. With Apple at least I’m not selling out my users immediately.

Re:Face ID and Touch ID for the Web by variaga on Monday October 19, 2020 @07:12PM (#24832096)
This is why (as a customer) I always prefer "yet another web account" vs. "sign-in with ____" - yes, it's a hassle to manage a different account for every different thing I use (although not much of one with a decent password manager), but I get the advantage of not risking losing access to _everything_ because <list of all the things that might go wrong with a sign-on provider>.

Single-sign-on means single point of failure.

Re:Face ID and Touch ID for the Web by derefr on Monday October 19, 2020 @09:11PM (#24833032)
Is that still true when those accounts are literally just backend-side caches of your shipping+billing address and credit card details?

I had to create an "account" to order a pizza. That account does nothing other than to make ordering pizzas slightly faster. I would be literally not inconvenienced at all if I had to input all that information for each order (because AutoFill.) I would also be literally not inconvenienced in the slightest if I lost access to that account and had to create another one.

To me, that's the type of "account" for which "Sign In With Apple" is a perfect solution. The type of account where it's only the provider insisting on having an account in the first place, and you would be get on just fine without one if they'd let you.

(Or, for an even more annoying example: web forums that you have to "create an account" for to read certain posts, or download attachments on those posts. Thanks for making me take five minutes to verify my email just so I can click a link on a page!)

Re:Face ID and Touch ID for the Web by ogre_codes on Monday October 19, 2020 @11:00PM (#24833550)
I suppose it depends entirely on what the account is securing.

My bank? Needs to be pretty independent of everything else.

Some random web store or something like Kickstarter? The only reason I care about those accounts is to track orders or for the convenience of not having to re-enter credit card info. The risk of losing my Apple account because ??? and dealing with recreating those accounts is negligible. In many cases I just use guest login for exactly that reason.

The convenience accounts are the ones I might use Sign in with Apple for. The bank? Not so much. But I won't trust Google or Facebook with even the convenience accounts.

I would also use something like this Touch ID on the web feature for 2FA, particularly if the only other options are SMS or email.

Re:Face ID and Touch ID for the Web by stickfigure on Tuesday October 20, 2020 @12:51AM (#24834028)
> I wouldn’t bet my company on any sign in with _____ service.

With Google Sign-In, you get an email address. If push comes to shove, you rip out the Google code and email everyone a traditional password.

Re:Face ID and Touch ID for the Web by mushufasa on Monday October 19, 2020 @05:15PM (#24831104)
You could say that about anything -- nothing is completely static -- but it's worth mentioning that Apple vs. Epic is a counterexample; Epic wants apple to change their policies (lower than 30% cut) while Apple wants to maintain the same structure since the inception of their app store.
Re:Face ID and Touch ID for the Web by throwaway894345 on Monday October 19, 2020 @05:54PM (#24831472)
> You could say that about anything -- nothing is completely static

1. Contracts are a thing. You can draft a contract with your vendor that guarantees certain terms for a certain duration.

2. You should be wary of wandering into commitments (including de facto commitments e.g. "vendor lock-in")--there are plenty of good reasons to do so, but one should make sure to properly consider the cost.

The problem is that doing business with Apple can make or break a company--companies can scarcely afford not to do business with Apple. I'm not an economist, but this seems pretty monopolistic (which isn't to say Apple should be broken up, but perhaps more tightly regulated).

Re:Face ID and Touch ID for the Web by ogre_codes on Monday October 19, 2020 @06:31PM (#24831754)
It is more of an monopsony[1] than a monopoly. If you are looking to buy a smartphone there are still options. If you are looking to sell software for smart phones, Apple is by far the most lucrative platform and they have a lock on publishing software for iOS. It is very difficult in the US to survive as a software developer for Android only.

The anti-trust frameworks in the US are based largely on monopolies and there is little in the way of legal precedence for protecting sellers in a monopsony market. If Epic wins their legal battle, it will likely set precedence for later cases.

Google and Facebook are also largely in weird legal ground. They have more or less exclusive access to large networks of users which is hugely disruptive to the advertising market.

[1] A monopoly is a market where there is only one provider. A monopsony is a market where there is only one buyer.

Re:Face ID and Touch ID for the Web by throwaway894345 on Monday October 19, 2020 @08:10PM (#24832523)
Perhaps I should have said “anti-competitive”. As you note, it’s very difficult to survive as an app developer on other platforms, and that’s bad for users ultimately.

I would like to see the US crack down on anti-competitive behavior in general, but especially in cases where companies are deriving value by gate-keeping some large network. To this effect, I think Apple is a relatively minor problem compared to social media networks. Consumers have no meaningful choice (hopefully I don’t need to elaborate on why Facebook vs Twitter is a false choice) and it allows social media companies to get away with all kinds of awful behavior, but especially the ability to steer the course of democracy (by determining at scale who is exposed to which ideas and at what potency) and then selling that as a service to the highest bidder or even serving as an attack vector for other states to steer our democracy (or other democracies for that matter). A monopoly over the flow of speech is intolerable for a democracy, and at least in America where conservatives are concerned about censorship of conservative speech by Silicon Valley progressives and liberals are concerned about Russian manipulation, it seems like a naturally bipartisan concern.

Edit: genuinely wondering what downvoters are objecting to in particular? Do you not believe that social media companies have a monopoly over their own networks? Do you disagree that they can and do steer public opinion and thus public policy? Do you disagree that this is a bad outcome? Perhaps it’s a bad outcome but regulation is an ineffective solution (e.g., libertarianism)? Educate me.

Re:Face ID and Touch ID for the Web by gowld on Monday October 19, 2020 @07:07PM (#24832052)
Apple sits between users and developers. If it's a monopsony on one side, it's a monopoly on the other side.
Re:Face ID and Touch ID for the Web by ogre_codes on Monday October 19, 2020 @11:06PM (#24833569)
Not remotely. Users can buy Android phones.

Having ~50% market share is not a monopoly.

Even suggesting Apple has monopsony as I did above is a stretch and is only the case if you define the market based on paying users.

Re:Face ID and Touch ID for the Web by throwaway894345 on Monday October 19, 2020 @11:12PM (#24833611)
The monopoly/monopsony distinction is pedantry. The important point is that consumers and developers suffer because one company controls access to the lion’s share of a market. That point can be criticized and debated, but litigating semantics makes for boring reading and anyway it’s off topic.
Re:Face ID and Touch ID for the Web by ogre_codes on Tuesday October 20, 2020 @12:26AM (#24833917)
> The monopoly/monopsony distinction is pedantry.

Expecting people to be in the general ballpark of the definition of a thing isn't pedantry. It's kind of hard to have any sort of meeting of the minds when people ignore even the basic premise of a term.

Re:Face ID and Touch ID for the Web by ascorbic on Tuesday October 20, 2020 @02:10AM (#24834376)
> Having ~50% market share is not a monopoly.

Most competition regulators disagree. 50% of a market is well above the threshold for both the US and EU to consider a company to be a monopoly. They usually treat the cut-off as around 20%.

Re:Face ID and Touch ID for the Web by stouset on Monday October 19, 2020 @10:03PM (#24833294)
How does this argument not apply to Facebook and Google?

Hint: It does, 100%. Epic could pick a fight with Google, tomorrow, that culminates in the same exact outcome.

Re:Face ID and Touch ID for the Web by enos_feedler on Monday October 19, 2020 @06:13PM (#24831608)
It isn’t productive to establish defense against an arbitrary future that turns on you. Spend those brain cycles focusing on your user and building a great product. Choosing Sign in with Apple is great for Apple users.
Re:Face ID and Touch ID for the Web by vinceguidry on Monday October 19, 2020 @06:19PM (#24831662)
It absolutely can be productive. So many people have done as you said and had the rug ripped out from under them by $ARBITRARY_PLATFORM_DECISION (cough cough YouTube) that if they had thought the risk they were taking on by going with one platform they might still be in business.
Re:Face ID and Touch ID for the Web by enos_feedler on Monday October 19, 2020 @08:31PM (#24832689)
I heard a guy died getting struck by lightning once. I am _never_ leaving my house during a storm again.
Re:Face ID and Touch ID for the Web by asdfasgasdgasdg on Monday October 19, 2020 @06:30PM (#24831742)
Maybe so. But how is this different than saying, "I have nothing to hide, so I'm not worried about having my car searched?" It's a somewhat pragmatic point of view but I wonder if it is a good idea in the limit.
Re:Face ID and Touch ID for the Web by enos_feedler on Monday October 19, 2020 @08:37PM (#24832758)
So what are you saying then? We shouldn't agree to a system that allows our car to be searched because under some limit it might be bad for us? What are we comparing this to in the Apple case? What is the equivalent of the "car search"?
Re:Face ID and Touch ID for the Web by gowld on Monday October 19, 2020 @07:04PM (#24832018)
"I have nothing to hide, so I'm not worried about having my car seized"
Re:Face ID and Touch ID for the Web by Teever on Monday October 19, 2020 @06:38PM (#24831803)
> It isn’t productive to establish defense against an arbitrary future that turns on you.

It isn't?

Isn't that like, the hallmark of intelligence?

Re:Face ID and Touch ID for the Web by danudey on Monday October 19, 2020 @07:09PM (#24832064)
Against an arbitrary future? No. Against a likely future? Yes.

It is not the hallmark of intelligence to come up with every possible thing that could go wrong and build defenses against it just in case someone somewhere does something counter to their wellbeing.

If you use any third-party login system, think about how you can migrate users between accounts, or validate that they are who they say they are, that's perfectly normal. What if Twitter OAuth goes down? What if your Google dev account is suspended by some automated system for some reason? You should definitely have some kind of plan for that.

Spinning off contingencies in case Apple changes its developer policies out from under you and suddenly no one on iOS can log in? Too specific and arbitrary.

Re:Face ID and Touch ID for the Web by enos_feedler on Monday October 19, 2020 @10:05PM (#24833312)
I think you watch too much Doomsday Preppers
Re:Face ID and Touch ID for the Web by wtetzner on Monday October 19, 2020 @04:52PM (#24830879)
> or the headache of managing yet another web account.

Honestly, I find this to be the distant second behind no account. I treat my password manager as my SSO provider in some sense.

Re:Face ID and Touch ID for the Web by qppo on Monday October 19, 2020 @04:50PM (#24830870)
I've had an issue with sign-in with Apple where using an autogenerated emails ruins certain support interactions. One of them was cancelling a subscription service that was eventually resolved (they required me to email their customer support, which I couldn't figure out how to do using the autogenerated email address created by "sign-in with Apple").
Re:Face ID and Touch ID for the Web by matthewmacleod on Monday October 19, 2020 @05:47PM (#24831409)
While it’s frustrating and worth pointing out of course - what really happened there was a bug in the service provider’s support process!
Re:Face ID and Touch ID for the Web by qppo on Monday October 19, 2020 @05:55PM (#24831477)
It was actually a dark pattern, not a bug.
Re:Face ID and Touch ID for the Web by tchalla on Monday October 19, 2020 @08:10PM (#24832522)
It would be helpful if you could let us know how you managed to send that e-mail.
Re:Face ID and Touch ID for the Web by mr_toad on Monday October 19, 2020 @09:19PM (#24833076)
You can see the email that Apple generates:

https://support.apple.com/en-us/HT210426

Re:Face ID and Touch ID for the Web by tchalla on Tuesday October 20, 2020 @05:56AM (#24835570)
Yes but the situation I asked for a solution is different. It is not about not seeing the e-mail, it is about sending from the private e-mail. Example

You subscribe with `[email protected]` which relays to `[email protected]`. Customer support asks you to chat with them from the same ID you signed up. Your e-mail client sends email from `[email protected]`. How can you quickly respond to the customer support from `[email protected]`?

Re:Face ID and Touch ID for the Web by qppo on Tuesday October 20, 2020 @12:57PM (#24839704)
I didn't, I found an alternative that was specific to the service.
Re:Face ID and Touch ID for the Web by mszcz on Tuesday October 20, 2020 @03:16AM (#24834650)
> convenience, security, and privacy of Sign in with Apple over Google, Facebook

Unless of course they block you for whatever reason. Then the process of getting back access has nothing to do with convenience, security, and privacy...

Re:Face ID and Touch ID for the Web by krtkush on Monday October 19, 2020 @04:11PM (#24830422)
> I would definitely stay away from any "Sign in with Apple".

I would stay away from any "Sign in with.." service as a user and as a product owner. You're affectively giving away a major control of your users to a third party.

Re:Face ID and Touch ID for the Web by yegle on Monday October 19, 2020 @04:19PM (#24830516)
I think "Sign in with Apple" is unique that Apple allows the users to hide their email address https://support.apple.com/en-us/HT210425 which makes it extremely hard to migrate away, unlike other federated login system where you can at least get users' email addresses, allowing you to create a proper email+password login later on.
Re:Face ID and Touch ID for the Web by the_arun on Monday October 19, 2020 @05:21PM (#24831163)
I think it is very private. The third party app cannot sell the attached email address to others. But I agree if you sign up with the third party using your apple id, they will not know you which may end up in creating second account. If they don't have account linking feature, it will be messy.
Re:Face ID and Touch ID for the Web by dkonofalski on Monday October 19, 2020 @06:04PM (#24831547)
Apple announced an account linking feature as a requirement at WWDC this year.
Re:Face ID and Touch ID for the Web by gowld on Monday October 19, 2020 @07:11PM (#24832087)
How is that? It's the developer's choice of they want to let me add a second login to the same account.
Re:Face ID and Touch ID for the Web by KMnO4 on Monday October 19, 2020 @04:22PM (#24830550)
As a product owner, why wouldn't I want to piggyback on the millions of dollars of R&D + security that the big companies have put in?

And as a user, why would I trust my password to the website that rolled their own authentication over the big companies?

Re:Face ID and Touch ID for the Web by danShumway on Monday October 19, 2020 @05:25PM (#24831205)
> why would I trust my password

Other people have mentioned this, but if you're not reusing passwords, this shouldn't be a concern for you. Don't reuse passwords!

On the security front, companies that are implementing 3rd-party sign-in can still get hacked and leak your personal information. If that information is supplied by Apple instead of you, it's all the same. You don't automatically get better security because you're using 3rd-party sign-in, you only get better security if you're being forced to stop doing something bad (reusing passwords, enabling 2FA) or if Apple is providing less information than an account would ask for during signup.

To Apple's credit on that front, they do mask your email, which is a legitimate privacy improvement. But it would be better for that to be a generic service that allowed you to generate an anonymous email at any time for anything, rather than a perk that's hardwired into an anti-competitive scheme to make it harder for you to migrate devices or change services.

Re:Face ID and Touch ID for the Web by chrisshroba on Monday October 19, 2020 @04:32PM (#24830678)
As a product owner, because what if that service provider decides to (mis-?)interpret something you did as against their TOS and revoke your access to their sdk, thereby making it more difficult for many of your users to log in?

And as a user, what if Facebook/Google/Twitter/Apple decides you've violated their ToS, blocks you from your account, and now you can no longer log into any of the sites you've linked with one of those providers?

I know this is a bit extreme, and for many people, the risk is totally worth the reward, but I think that is one of the chief concerns many people have with trusting a third party for all their sign-ins. It's a single point of failure.

Re:Face ID and Touch ID for the Web by xenocratus on Monday October 19, 2020 @04:31PM (#24830665)
> why would I trust my password...

Do you use the same password everywhere, by any chance? :)

Re:Face ID and Touch ID for the Web by ethbr0 on Monday October 19, 2020 @05:28PM (#24831231)
I used to, but some websites stopped accepting "abc123"!

Thankfully, it's still fine for my bank login.

Re:Face ID and Touch ID for the Web by hawkoy on Monday October 19, 2020 @06:16PM (#24831634)
As a user, I recently deleted x account. I used login with x on a few services and now I can't access them anymore.

This situation is solvable by implementing forget password and storing user's email but many services don't and with a system similar to apple's where you mask the email or phone number, you can't do anything.

Re:Face ID and Touch ID for the Web by ts330 on Monday October 19, 2020 @04:32PM (#24830675)
this is a MASSIVE selling point, BUT, when your users contact support trying to gain access to their account and can't describe what their email address might be... trust me, there is pain in your future.
Re:Face ID and Touch ID for the Web by gowld on Monday October 19, 2020 @07:10PM (#24832071)
Users can just tell the vendor what their real email address is when they want support, until Apple bans vendors who ask for contact info.
Re:Face ID and Touch ID for the Web by manigandham on Monday October 19, 2020 @10:58PM (#24833541)
It's true that oauth is very secure but I wouldn't assume major sites are rolling their own authentication. The standard password hashing methods and workflows are all well known and implemented.

Even if the local auth system was poor, an email/password combo is simpler and faster without leaking data to social providers. There's no reason to remember which provider you used, or login to them first, or worry about loose permissions especially with future changes. It also limits the blast radius in case your social account ever gets compromised, and it's useful for completely anonymous and disposable accounts.

Re:Face ID and Touch ID for the Web by karlshea on Monday October 19, 2020 @04:45PM (#24830821)
Well one issue as a user is trying to remember which third-party auth was used when I first created the account (did I use Facebook? Google? Twitter?).
Re:Face ID and Touch ID for the Web by hawkoy on Monday October 19, 2020 @06:23PM (#24831685)
Well, you can get access to the email on all three so it's not a huge problem for vast majority of whom only maintain single email address.
Re:Face ID and Touch ID for the Web by Aeolun on Monday October 19, 2020 @08:17PM (#24832579)
Mainly to prevent the big companies from knowing every website you’ve ever visited.
Re:Face ID and Touch ID for the Web by mooreds on Monday October 19, 2020 @05:01PM (#24830980)
This is always a business decision, imo.

It's similar to publishing on medium (or Huffpost, from a few years ago) as opposed to your blog. You'll get more reach in the former case, but have much less control. For that matter, it's similar to serverless vs code everything and host it in a server on a rack somewhere.

Engineering is all about the tradeoffs.

So, how would I make that call? I'd think about how much it mattered to have control of the auth experience vs the easier onboarding of customers. I'd think about the risks of having the auth yanked out from under me (I'm not aware of any cases where this happened). I'd think about the value add of auth to my app; in most cases it's slim to none. I'd also look at what the auth provider allowed me to know about the user when they deliver an authenticated user to my application.

I think in general auth isn't a huge differentiator for most applications, and offloading it to a social provider, as long as a chunk or most of the target market has an account (github for devs, linkedin for sales folks, google for, well, people with an email address), is a good choice.

Don't forget, you can provide both; I've worked at companies with only social login, but don't think that's very common.

Disclosure, I now work for a company which provides auth software (link in my bio).

Re:Face ID and Touch ID for the Web by gowld on Monday October 19, 2020 @07:12PM (#24832100)
It's extremely cheap to syndicate to Medium plus other venues. Not so for Sign In With.
Re:Face ID and Touch ID for the Web by mooreds on Tuesday October 20, 2020 @11:46AM (#24838736)
What is expensive about "sign in with"? There are lots of libraries that will make it pretty simple, though the configuration can be hairy (google, looking at you).

It's more expensive than syndicating content, sure, but I think you want to compare the relative costs of each option, not between them.

Write on medium vs writing on your own blog

Using social sign on vs building your own auth system (hopefully using a library)

Re:Face ID and Touch ID for the Web by Angostura on Monday October 19, 2020 @04:27PM (#24830618)
As a user, I'm much happier giving my e-mail address to Apple who already has it, then 100 other websites.
Re:Face ID and Touch ID for the Web by brightball on Monday October 19, 2020 @04:25PM (#24830586)
I always leaned that way, but from the security and compliance side of things it's a heck of a lot easier for us when our staff can sign into 3rd party services with their company Google account that has strict security and 2 security keys in place vs whatever the luck of the draw may be with each service that we want to use. It's a nice alternative to the "SAML SSO only available with $10k / user enterprise account" routine.

But as long as that service has quality 2FA options with (ideally) Webauthn, it's much less of a concern.

Re:Face ID and Touch ID for the Web by gremlinsinc on Monday October 19, 2020 @04:20PM (#24830532)
so, if you're a service that posts memes to twitter, or facebook you should always use email and sms two factor, no 'sign in with facebook/twitter' links?
Re:Face ID and Touch ID for the Web by outworlder on Monday October 19, 2020 @04:35PM (#24830714)
> You're affectively giving away a major control of your users to a third party.

You may also get users that you wouldn't have otherwise. It's a trade-off. Lowering friction tends to increase conversions.

Re:Face ID and Touch ID for the Web by tshaddox on Monday October 19, 2020 @04:13PM (#24830449)
Even if you don’t like Apple’s actions in the whole Epic drama, one thing that’s clear from it is that Apple probably won’t terminate your developer account like this unless you beg them to as part of a major PR stunt.
Re:Face ID and Touch ID for the Web by yegle on Monday October 19, 2020 @04:16PM (#24830481)
But they can expand the prohibited uses clause in the future if they see fit. https://developer.apple.com/sign-in-with-apple/usage-guideli...
Re:Face ID and Touch ID for the Web by parasubvert on Tuesday October 20, 2020 @07:19AM (#24836094)
Contracts can be changed based on pre-agreed terms, film at 11

At some point, people need to do business. Worrying about hypotheticals leads to paralysis.

Re:Face ID and Touch ID for the Web by thefounder on Monday October 19, 2020 @04:16PM (#24830479)
>> Apple probably won’t terminate your developer account

Or probably they will terminate it if they don't like your business

Re:Face ID and Touch ID for the Web by madeofpalk on Monday October 19, 2020 @05:15PM (#24831100)
For what it's worth, it's been said (by anonymous sources, no one on the record) that Apple did not threaten to terminate Epic's "Sign in with Apple" accounts/features, and they spent extra effort to maintain their access to that after their account was terminated.

I do not know if other terminated accounts get this "luxury".

Re:Face ID and Touch ID for the Web by wlesieutre on Monday October 19, 2020 @05:57PM (#24831496)
Epic did say it was going to be terminated, presumably as part of the overall account termination. They then updated that it would continue to work.

https://www.theverge.com/2020/9/10/21431396/epic-sign-in-wit...

Apple commented they weren’t doing anything to stop Sign In with Apple working, but I have to wonder if there’s a lie of omission in there. Like “We aren’t doing anything deliberate to stop it, but it’s going to stop as a side effect of terminating their developer account.”

Either that or Epic was lying outright.

Re:Face ID and Touch ID for the Web by girvo on Monday October 19, 2020 @06:31PM (#24831750)
Considering the court itself has said Epic has lied about other details, I’d lean towards that.
Re:Face ID and Touch ID for the Web by madeofpalk on Monday October 19, 2020 @06:12PM (#24831604)
unnamed sources have said that Epic was outright lying https://daringfireball.net/linked/2020/09/29/epic-games-unre...

> multiple sources at Apple told me Epic’s claims were simply false. There was never a September 11 deadline for their SIWA support to stop working, and in fact, Apple’s SIWA team performed work to make sure SIWA continued working for Fortnite users despite the fact that Epic Games’s developer account had been revoked.

Re:Face ID and Touch ID for the Web by dirtae on Tuesday October 20, 2020 @01:34AM (#24834203)
Re:Face ID and Touch ID for the Web by wlesieutre on Monday October 19, 2020 @06:47PM (#24831880)
So the other question, is this a standard behavior, or a special circumstance because of Epic's high profile?

Or more to the point, if Apple terminates your developer account, do you think Apple's SIWA team will "perform work to make sure SIWA continues working" for your users?

If work is actually required, I'm not optimistic.

Re:Face ID and Touch ID for the Web by ksec on Tuesday October 20, 2020 @03:09AM (#24834614)
That is the problem with KOL, spreading wrong information and it spreads as Fact.

Gruber was also the one who spread the Safari Javascript is so much faster than its competitor because Apple have custom SoC and they use specialise ARM instruction to speed it up. And now even HN has a high percentage of people who believe in that without even thinking about it.

And like I said in the previous thread on HN about misinformation. None of these KOL, and including most media / publication care to fact check or to correct their previous wrong reporting.

Re:Face ID and Touch ID for the Web by ksec on Tuesday October 20, 2020 @03:06AM (#24834608)
You were right. And this is not the first time Tim Cook's Apple caught outright lying, or Lie of Omission. And not in any good faith.

In both Qualcomm and in IMG's Case.

The whole new Tim Cook's PR and Marketing is way worst than Steve's era in my book. Along with their business strategy and behaviour.

Re:Face ID and Touch ID for the Web by floatingatoll on Monday October 19, 2020 @04:35PM (#24830720)
It's weird to see you using this example, given that Apple specifically went out of their way to continue operating Sign in with Apple for all of Epic's users. Can you talk more about why you would stay away from it when developing for Apple platforms?
Re:Face ID and Touch ID for the Web by danudey on Monday October 19, 2020 @07:05PM (#24832024)
Note that Epic claimed that "Sign in with Apple" was going to get terminated, but Apple says that wasn't true:

https://www.theverge.com/2020/9/10/21431396/epic-sign-in-wit...

And IIRC it all still works anyway, so this sounds like Epic either being confused about itself or lying to make Apple look like the bad guy (more).

And bear in mind that anyone using any third-party auth (like Twitter, Facebook or Google OAuth) could have their developer accounts terminated for violating the rules, same as Apple. I guess the key takeaway here is "if you're relying on someone else's services, don't flagrantly disregard the service's rules publicly in order to start a lawsuit and then try the case in the court of public opinion", but I think that's good advice for any service.

Re:Face ID and Touch ID for the Web by dirtae on Tuesday October 20, 2020 @01:36AM (#24834214)
Re:Face ID and Touch ID for the Web by dwaite on Monday October 19, 2020 @04:02PM (#24830324)
Apple did not terminate Epic's SiwA account, and several journalists have sources within Apple that say that Apple never sent the message Epic claimed to receive that said access was going away.
Re:Face ID and Touch ID for the Web by virtue3 on Monday October 19, 2020 @04:06PM (#24830366)
https://developer.apple.com/forums/thread/123774

Not the only ones that randomly gets their accounts terminated.

Based on how apple has -insane- fragmentation and security for different aspects of the company, I would doubt any employee that isn't directly tied into the store accounts would know the whole details. (Source: GF worked for the department that did art/design for the apple stores, no one had access to their room, and they had more secure rooms that only a few employees had access to).

FWIW google has the same issues.

Don't trust a company with an account that you can't get a human on the phone for to review shit.

Re:Face ID and Touch ID for the Web by toomuchtodo on Monday October 19, 2020 @04:23PM (#24830554)
I use Sign In with Apple everywhere I can (so many of my passwords are in haveibeenpwned datasets), and if Apple blacklisted a provider I use, I’d expect the service to email me to migrate to their own email/password identity provider (if I didn’t hide my email from them with SIWA), with a link to the migration process in the email.
Re:Face ID and Touch ID for the Web by dkonofalski on Monday October 19, 2020 @06:15PM (#24831625)
Same except that, if Apple blacklisted a provider, I'd want to know why they got blacklisted. At this point, I trust Apple as a neutral third party more than I trust most other companies since Apple isn't incentivized to sell my info.
Re:Face ID and Touch ID for the Web by toomuchtodo on Monday October 19, 2020 @06:24PM (#24831693)
Agreed, with the caveat that we need some regulation through legislation to codify safeguards around identity providers, their responsibilities, etc.
Re:Face ID and Touch ID for the Web by mvanbaak on Monday October 19, 2020 @04:23PM (#24830556)
> Not the only ones that randomly

Not really random now right...

Re:Face ID and Touch ID for the Web by dwaite on Monday October 19, 2020 @06:23PM (#24831684)
That does not necessarily have anything to do with SiwA, however.
Re:Face ID and Touch ID for the Web by saagarjha on Monday October 19, 2020 @04:12PM (#24830439)
Tim Sweeney produced a letter saying that Apple would terminate their access: https://twitter.com/TimSweeneyEpic/status/131134525357683097...
Re:Face ID and Touch ID for the Web by jsjohnst on Monday October 19, 2020 @08:19PM (#24832589)
That’s a pretty misleading interpretation of what Apple said or even what Tim Sweeney said in the tweet...
Re:Face ID and Touch ID for the Web by saagarjha on Monday October 19, 2020 @08:32PM (#24832702)
How so?
Re:Face ID and Touch ID for the Web by jsjohnst on Monday October 19, 2020 @11:48PM (#24833764)
> Apple is entirely in its rights to terminate Epic Games’ developer account and all related functionality, but SIWA will continue to function for two weeks.

Ok, let’s translate it:

1) Apple believes it’s entirely in its rights to terminate Epic’s dev account and is doing so

2) Apple also believes it’s in their right to kill all related account functionally, but they aren’t, specifically with SIWA, for at least two weeks.

3) they don’t specify what will happen after two weeks, as that likely depends on several factors. We later learn that they extended it indefinitely.

So there’s multiple possible scenarios:

A) Apple really is just threatening as you indicated, but not being blatantly direct about it. Possible, but not the only possibility, and not usually their style from what I’ve seen for something like this, but who knows. I feel if Apple really wanted to threaten, they’d make the threat explicit and say “after two weeks of non-compliance, we will terminate everything”.

B) Apple is stalling making a decision over if SIWA will continue to be available to Epic’s users to ensure the SIWA team can support it when the dev account is deactivated. From other rumors where we hear folks saying SIWA team did have to make changes, I’m thinking this was the likely scenario. Don’t make a commitment to keep something going if you can’t deliver on it for sure yet, so “give them a two week extension” so you learn if you can actually keep SIWA up. If they can’t and Epic is still fighting with Fire, maybe you do terminate SIWA, but maybe not. Either way, Apple wins.

C) Apple is stalling a decision to scare Epic into compliance after Epic’s users backlash over word it might end. Possible, but I think Epic had well shown they were ready to play the Russian roulette game with Apple down to the last chamber, so I’m thinking less likely than A/B.

So if I was a betting man, I’d say it’s a mixed bag at best, but would likely go:

B > A > C

Apple doesn’t play checkers, they play chess. When they send a letter like that, they ensure there’s multiple positive outcomes for them for any potential scenario, from technical complications, to user perception, to legal proceedings, etc.

Re:Face ID and Touch ID for the Web by guptaneil on Monday October 19, 2020 @10:47PM (#24833481)
While there's always a risk anytime you build on top of someone else's platform, it's worth noting that it looks like Epic lied[0] about getting blocked from Sign in with Apple. There's no evidence they were going to lose access to it, even with a terminated developer account.

0: https://daringfireball.net/linked/2020/09/29/epic-games-unre...

Re:Face ID and Touch ID for the Web by dirtae on Tuesday October 20, 2020 @01:35AM (#24834205)
Re:Face ID and Touch ID for the Web by guptaneil on Tuesday October 20, 2020 @04:13AM (#24834977)
Ahh thanks for sharing that. That’s good to know. Super disappointed Gruber didn’t update his post with that information, especially given his recent campaign against editorial integrity.
Re:Face ID and Touch ID for the Web by davweb on Tuesday October 20, 2020 @09:40AM (#24837149)
Sign in with Apple still works for Fortnite. [1]

According to Epic, Apple said they were going to turn it off and then changed their minds. Apple's position is they were never going to turn off Sign in with Apple for Epic.

[1]: https://twitter.com/FortniteStatus/status/130416143288864358...

Re:Face ID and Touch ID for the Web by supah on Monday October 19, 2020 @07:41PM (#24832338)
Except the 2FA is kinda stupid.

I have devices logged into my iCloud account at a datacenter, that end up getting my 2FA for my other devices.

I have a iPhone, iPad, Macbook, do you think any device I actually use all the time gets the 2FA code ?

Sometimes, the same computer i’m using to login gets the code which is kinda pointless.

I have to always use SMS to get my code because of this.

Re:Face ID and Touch ID for the Web by xodice on Monday October 19, 2020 @08:39PM (#24832778)
Every single device on your iCloud account gets the 2FA prompt. You then choose which device you want to confirm the request on. The prompt does not go to just a single device, but every single device on said iCloud account.
Re:Face ID and Touch ID for the Web by dbt00 on Tuesday October 20, 2020 @12:37AM (#24833969)
Note that Epic claims Apple was going to disable "sign in with Apple", but Apple did not do so and has claimed through unattributed press quotes that they were never going to do so, that Epic made that up.
Re:Face ID and Touch ID for the Web by dirtae on Tuesday October 20, 2020 @01:37AM (#24834219)
Apple's claim is false, and can be shown to be false via documents in the court filing: https://twitter.com/TimSweeneyEpic/status/131134525357683097...
Re:Face ID and Touch ID for the Web by jbverschoor on Tuesday October 20, 2020 @06:28AM (#24835772)
Yeah same for me. I was super happy with sign in with apple as a concept, but I have exactly 1 account with them. After the epic account-hijacking, no thank you. I will never ever use it again.
Re:Face ID and Touch ID for the Web by benlivengood on Monday October 19, 2020 @08:16PM (#24832570)
Why don't sites start supporting multiple federated identities? It shouldn't be too hard to keep the "sign in with X" links on the account settings page, right?
Re:Face ID and Touch ID for the Web by beached_whale on Monday October 19, 2020 @06:10PM (#24831592)
Epic asked them to terminate the account though.
Re:Face ID and Touch ID for the Web by mvanbaak on Monday October 19, 2020 @04:22PM (#24830542)
you do know EPIC did break a lot of clauses in their contract, knowing what the impact of breaking these clauses was, and still breaking all those clauses?
Re:Face ID and Touch ID for the Web by otterley on Monday October 19, 2020 @04:03PM (#24830337)
> Having saw Epic's developer account terminated by Apple, I would definitely stay away from any "Sign in with Apple".

If you don't renege on your agreements with Apple as part of a public pissing contest, and you aren't in the business of misleading customers and creating deceptive apps, it's unlikely they'll revoke your developer account.

Re:Face ID and Touch ID for the Web by yegle on Monday October 19, 2020 @04:14PM (#24830456)
There's an explicit list of websites that are not allowed to integrate with "Sign in with Apple". https://developer.apple.com/sign-in-with-apple/usage-guideli... Nothing stops Apple from adding more requirements in the future, even if you don't start a feud with Apple.
Re:Face ID and Touch ID for the Web by reaperducer on Monday October 19, 2020 @04:20PM (#24830522)
There's an explicit list of websites that are not allowed to integrate with "Sign in with Apple".

I don't think anyone is crying over Apple not wanting to handle authentication for web sites offering "Illegal drugs or non-legally prescribed controlled substances."

The rest of the list is similar.

And yes, with that list Apple has once again affirmed it's not interested in helping normalize pornography. That's its choice.

Re:Face ID and Touch ID for the Web by yegle on Monday October 19, 2020 @04:43PM (#24830792)
Sure, but at the end of the page:

> Apple reserves the right to disable Sign in with Apple on a website or app for any reason at any time.

Re:Face ID and Touch ID for the Web by wayneftw on Monday October 19, 2020 @04:19PM (#24830517)
Wow, you can’t even use sign in with Apple if you

“Show Apple or its products in a false or derogatory light.”

Who decides what’s false or derogatory?

Re:Face ID and Touch ID for the Web by floatingatoll on Monday October 19, 2020 @04:37PM (#24830732)
A court of law.
Re:Face ID and Touch ID for the Web by danShumway on Monday October 19, 2020 @05:35PM (#24831284)
No, there's no world where Apple blocks access to an account because they're showing derogatory content towards Apple products, and a company gets a judge to overturn that block because it's not technically libel. Apple has the right to block you from their sign-in for any reason. Short of pulling a move like Epic and suing them for antitrust, a court of law is never going to enter into the equation.

None of these are legal definitions, Apple gets to decide what they mean. And no court of law is going to rule that they don't have the right to block when their TOS end with:

> Apple reserves the right to disable Sign in with Apple on a website or app for any reason at any time.

Re:Face ID and Touch ID for the Web by otterley on Monday October 19, 2020 @05:43PM (#24831356)
> Apple gets to decide what they mean.

(IAAL, this is not legal advice.)

That's not how contract law works. There's a whole body of law around how to construe language in contracts, and it's subject to litigation and dispute if the definition isn't made clear in the contract itself.

> no court of law is going to rule that they don't have the right to block

Then you don't know courts very well. Such clauses are still subject to the law and public policy. For example, no competent court is going to allow anyone to use an escape clause to terminate a contract with someone because of their race, age, or gender.

But yeah, if you use someone's services and then publicly talk trash about them? Why should they be forced to continue to do business with you?

Re:Face ID and Touch ID for the Web by danShumway on Monday October 19, 2020 @05:51PM (#24831445)
> But yeah, if you use someone's services and then publicly talk trash about them? Why should they be forced to continue to do business with you?

Do you really not see how saying, "businesses should be allowed to sever ties with people who say mean things" is different from saying, "the courts will decide whether or not you committed libel"?

> For example, no competent court is going to allow anyone to use an escape clause to terminate a contract with someone because of their race, age, or gender.

Do you think there's a difference between a court saying, "we're not going to allow you to sever a business relationship because of a protected characteristic", and "we're going to regulate what does and doesn't count as disparagement"?

Can you point me at an example of a business fighting a disparagement clause in a contract with language like this and winning, based on a court deciding that what they said didn't count as disparagement?

This is like the people who say they're going to sue Facebook for taking down posts because their definition of "misleading information" isn't specific enough. You can sue anyone for anything, but you're not going to win that case. Companies with contract language like this have broad leverage to wield their power in whatever way they see fit -- because for the most part courts have not ruled that escape clauses boiling down to "we can decide to ban you at any time for any reason" are illegal or unenforceable.

Re:Face ID and Touch ID for the Web by otterley on Monday October 19, 2020 @06:15PM (#24831619)
> Do you really not see how saying, "businesses should be allowed to sever ties with people who say mean things" is different from saying, "the courts will decide whether or not you committed libel"?

Of course I see that. Contract law and defamation law (tort) are separate domains. A court does not have to conclude that a party to a contract committed libel in order to determine that they are in breach for making disparaging remarks about the counterparty. The layperson might (understandably) believe that the analysis would be identical, but it is not. A finding of libel under tort law requires a multi-part test which I won't elaborate on here, and there are lots of defenses, too.

> Companies with contract language like this have broad leverage to wield their power in whatever way they see fit -- because for the most part courts have not ruled that escape clauses boiling down to "we can decide to ban you at any time for any reason" are illegal or unenforceable.

I think we're in violent agreement for the most part -- I'm just saying that your characterization is overbroad since obviously "any reason" is not quite "any reason." As engineers, we should strive to be as accurate as possible in our analyses and avoid hasty overgeneralizations.

At bottom, courts aren't generally inclined to force parties to do business with each other if one of them is no longer interested, there are no promises left to be fulfilled, and there's nothing binding them to an infinite term (which courts also don't like to enforce). Apple is not a common carrier or the government, and so they're treated just like anyone else for the purpose of contract law.

Re:Face ID and Touch ID for the Web by Dylan16807 on Monday October 19, 2020 @07:18PM (#24832151)
> But yeah, if you use someone's services and then publicly talk trash about them? Why should they be forced to continue to do business with you?

Nobody said they have to, just that it's very dangerous to depend on such a service. I say bad things about companies all the time!

Re:Face ID and Touch ID for the Web by Qahlel on Monday October 19, 2020 @04:08PM (#24830397)
unilateral agreements that one side can change on a whim is not something that one would call a fair agreement in the first place.
Re:Face ID and Touch ID for the Web by reaperducer on Monday October 19, 2020 @04:22PM (#24830547)
unilateral agreements that one side can change on a whim is not something that one would call a fair agreement in the first place.

Wait till you read the fine print in your cell phone contract.

Re:Face ID and Touch ID for the Web by otterley on Monday October 19, 2020 @05:12PM (#24831078)
Do you really think a company the size of Apple is going to separately negotiate terms of service with every developer that wants to publish an app?

Contracts of adhesion are just a part of life. We agree to them practically every day whenever we do business with a third party. And if you were in the other party's shoes, you'd do the same thing; otherwise you couldn't practically run a business.

Re:Face ID and Touch ID for the Web by olliej on Monday October 19, 2020 @04:22PM (#24830548)
Well, both companies do that - The various epic EULAs let them behave just as apple does, so they can't argue it's unfair unless they want all their existing EULAs to be invalidated as well.
Re:Face ID and Touch ID for the Web by Symbiote on Monday October 19, 2020 @04:09PM (#24830406)
But we can still avoid Apple services in support of those Apple doesn't like, open standards and free competition.