Timeline for OAuth 2.0: Benefits and use cases — why?
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 7, 2021 at 7:13 | history | edited | CommunityBot | replaced http://tools.ietf.org/html/draft with https://datatracker.ietf.org/doc/html/draft | |
| Jun 6, 2020 at 6:33 | comment | added | user84118 | If someone doesn't understand oauth. Explaining oauth using oauth terms rather than plain english doesn't seem productive. | |
| Oct 14, 2016 at 9:21 | comment | added | Aydin K. | Regarding the terminology: It would be better, if you would stick to the official names of the affected parties (authorization server, resource server, resource owner) instead of using unclear ones (client, server, user ..). | |
| Jan 6, 2014 at 16:46 | history | edited | Todd Menier | CC BY-SA 3.0 | Attempted to clarify what's meant by "content provider" and "server" by way of example, which I think helps in understanding what follows |
| Jul 21, 2012 at 1:57 | history | edited | Peter T | CC BY-SA 3.0 | fixed grammar |
| Sep 27, 2011 at 12:12 | history | edited | Peter T | CC BY-SA 3.0 | Note that the server never gets the user's credentials in three-legged OAuth |
| Sep 27, 2011 at 5:17 | vote | accept | tonyhb | ||
| Sep 27, 2011 at 5:15 | vote | accept | tonyhb | ||
| Sep 27, 2011 at 5:16 | |||||
| Sep 26, 2011 at 23:09 | history | answered | Peter T | CC BY-SA 3.0 |