WeChat ID
aaronpk_tv
-
I've been in mostly violent agreement with @smdiehl and others who call out cryptocurrency and its descendants for what they are—an end run around financial regulation at best, a massive fraud at worst. We all agree it makes no sense as a technology. But one thing worries me:
-
Join me and @vibronet tomorrow for another OAuth Happy Hour! This week seems like a good week to talk about what happens when "Sign In with Facebook" is down.
📅 Oct 7 4pm Pacific
https://www.youtube.com/watch?v=B3a3-JV-dl0 -
Thanks @aaronpk for the clarification 👍
So OAuth 2.1 is essentially OAuth 2.0 without the naughty bits :) -
Farasath Ahamed
https://twitter.com/farazath619
•
Oct 6
Thanks @aaronpk for the clarification 👍
So OAuth 2.1 is essentially OAuth 2.0 without the naughty bits :) -
Farasath Ahamed
https://twitter.com/farazath619
•
Oct 6
Noticed that the resource owner password and implicit grants are removed from the 2.1 (For obvious reasons :))
But doesn't that make the OAuth 2.1 framework backward incompatible with OAuth 2.0?
OAuth 2.1 kind of gives the feeling its a slight(minor) change from OAuth 2.0
Password and Implicit are already not part of OAuth 2.0 as described by the Security Best Current Practice. The 2.1 update is leaving them out so that you don't have to first learn about them and then read another doc telling you not to use them. -
Draft 4 of the OAuth 2.1 Authorization Framework is out!
https://www.ietf.org/archive/id/draft-ietf-oauth-v2-1-04.html
I am especially excited to see @tlodderstedt working on this who is one of the authors of the OAuth 2 Security Best Practice doc.
https://datatracker.ietf.org/doc/html/draft-ietf-oauth-security-topics -
New version available! "The OAuth 2.1 Authorization Framework" https://www.ietf.org/archive/id/draft-ietf-oauth-v2-1-04.html by @DickHardt @aaronpk @tlodderstedt #oauth #oauth2 #ietf
-
