Q6: What are the four core roles defined in the OAuth 2.0 framework (RFC 6749)?
OAuth 2.0 defines four distinct roles to separate token authorization from resource handling:
- Resource Owner: The entity capable of granting access to a protected resource (typically the end user).
- Resource Server: The API server hosting the protected user resources, capable of accepting and responding to protected resource requests using access tokens.
- Client: The application making resource requests on behalf of the Resource Owner with its authorization.
- Authorization Server: The server issuing access tokens to the client after successfully authenticating the resource owner and obtaining authorization.
Key Takeaways
- OAuth 2.0 strictly decouples the Authorization Server from the Resource Server.
- Clients interact with Resource Servers strictly using access tokens issued by the Authorization Server.