OAuth 2.0
Definition
OAuth 2.0 enables limited access rights for an application.
An authorization framework by which a client obtains limited access to protected resources, often on behalf of a resource owner. OAuth 2.0 does not define user login.
Simply explained
An application receives a key for certain permitted actions, not automatic access to everything.
Why it matters in practice
Helps develop and operate digital systems robustly, securely, and maintainably.
Example from business
An application receives a short-lived token for clearly limited API access.
Limits and pitfalls
- Using OAuth alone as a login protocol, employing outdated flows, storing tokens insecurely, or overly broad redirect URIs and permission scopes.
Origin & history
OAuth 2.0 was published in 2012 as RFC 6749 and later supplemented by security best practices.
Use in mid-sized companies
- Possible example: An application receives a short-lived token for clearly limited API access.
Frequently asked questions
What does OAuth 2.0 mean?
An authorization framework by which a client obtains limited access to protected resources, often on behalf of a resource owner. OAuth 2.0 does not define user login.
Which mistakes should be avoided?
Using OAuth alone as a login protocol, employing outdated flows, storing tokens insecurely, or overly broad redirect URIs and permission scopes.
Sources
Source checked on 10.10.2026. Editorial application examples are hypothetical; no proof of real customer results.
Editorially reviewed on: