OAuth related standards supported by the Curity Identity Server.
This article demos best practices for using the OAuth for mobile applications.
Secure Single Page Applications using OAuth
What is PAR, and how does it help improve security for financial-grade APIs?
Add another security layer by requiring proof of possession.
Authenticating a client using certificates.
The OAuth Revoke Flow Explained.
The OAuth Refresh Flow Explained.
The OAuth Device Flow Explained.
The OAuth Resource Owner Password Credentials Flow Explained.
The OAuth Client Credentials Flow Explained.
The OpenID Connect Hybrid Flow Explained.
The OAuth Implicit Flow Explained.
What is DPoP and how it improves the security for public clients.
The OAuth Code Flow Explained.
An overview of how the Proof Key for Code Exchange should be used.
OAuth 2.0 is the industry-standard protocol for authorization and access delegation. It specifies a process for resource owners to authorize third-part access to their resources without sharing their credentials. OAuth facilitates fast and secure authentication and authorization for users to APIs, servers, devices and apps. It does this without sharing password information and instead uses access tokens to prove an identity, keeping user credentials safe.