News for hackers. Stuff that matters.
Re:Bypassing GitHub's OAuth Flow with a Head Request by hirsin on Thursday November 07, 2019 @11:05AM (#21474395)
Facebook does this when you sign into an app you've previously authorized, in native application flows. Microsoft just added this recently as well. We do recommend it to other IDPs.

This is only enforced for public clients though that don't have verifiable reply URIs - so web sites are OK.

Re:Bypassing GitHub's OAuth Flow with a Head Request by couchand on Thursday November 07, 2019 @12:38PM (#21475265)
I've only ever implemented web-based OAuth flows, so I haven't seen that behavior.

Do they also disallow the use of refresh tokens? It would seem that allowing refresh would let a malicious app get around the requirement.

Re:Bypassing GitHub's OAuth Flow with a Head Request by hirsin on Thursday November 07, 2019 @02:25PM (#21476423)
If you force a check at the start, refresh token seems fine. That's much preferable than popping ux every hour or whenever the access token expires.
Re:Bypassing GitHub's OAuth Flow with a Head Request by couchand on Friday November 08, 2019 @09:45AM (#21482596)
Then what's the point? The malicious app would just keep refreshing so you never see the confirmation again, anyway.