OAuth 2.0/OpenID Connect in general
OAuth 2.0 / OpenID Connect must be considered a framework for designing solutions to delegate access. The framework allows for a lot of flexibility.
- For any solution designed in this framework, be aware of the following:
- The fact that a solution follows the OAuth 2.0 specification does not imply that the solution is secure. To obtain secure solutions, one must specifically design them for the security requirements at hand and ensure their security using appropriate measures such as, but not limited to:
- security consulting,
- internal and external security reviews in the design,
- implementation and integration phase,
- penetration tests.
- The framework has been designed to allow access delegation. However, OAuth 2.0 is often employed to implement single sign-on (i.e., to achieve authentication goals). Historically, this has led to many vulnerable authentication solutions. We would like to stress our recommendation (1.), especially in this case.