Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

2
  • Thanks for a wide angle, but I don't think these advantages, (a) letting the user agent hold just the token instead of the password, (b) allowing a password change without disrupting existing client apps, (c) allowing users log out other sessions are specific to token authentication flows. Neither Basic nor token authentications mention functions (b) and (c) in their specs. Implementing (b) and (c) seems possible for any kind of authentication. It would involve keeping track of passwords (preferably their hashes). The advantage (a) seems dependant on the wider scope of the password. Commented Feb 26, 2019 at 20:23
  • 1
    How could we use OAuth if user (Resource Owner) doesn't have any credentials with an external Authorization server, but he has credentials in the Client application? That is we have Resource Owner (user), The Client (representing the user & also containing credentials for user) and Resource Server. How can a Resource Server authenticate & authorize the user? Commented Mar 14, 2019 at 6:13