Cookie Settings
Customize Consent Preferences

We use cookies to help you navigate efficiently and perform certain functions. You will find detailed information about all cookies under each consent category below.

The cookies that are categorized as "Necessary" are stored on your browser as they are essential for enabling the basic functionalities of the site. ... 

Always Active

Necessary cookies are required to enable the basic features of this site, such as providing secure log-in or adjusting your consent preferences. These cookies do not store any personally identifiable data.

No cookies to display.

Functional cookies help perform certain functionalities like sharing the content of the website on social media platforms, collecting feedback, and other third-party features.

No cookies to display.

Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics such as the number of visitors, bounce rate, traffic source, etc.

No cookies to display.

Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.

No cookies to display.

Advertisement cookies are used to provide visitors with customized advertisements based on the pages you visited previously and to analyze the effectiveness of the ad campaigns.

No cookies to display.

Other cookies are those that are being identified and have not been classified into any category as yet.

No cookies to display.

user authenticating

OAuth 2.0 Security Best Current Practice


OAuth 2.0 is a deceptively simple protocol. For many of us, we create a client id, client secret, set a few environment variables, and watch the black magic take effect. It turns Auth into a Boolean on/off switch. Great! But, what are the best practices for how to configure and use it if we are a bit more behind the scenes? Read on!

First, lets understand some of the threats and security considerations for OAuth 2.0. This is covered in much more detail in “OAuth 2.0 Threat Model and Security Considerations“.

You can see many more details in the IETF Draft “OAuth 2.0 Security Best Current Practice“.

https://tools.ietf.org/html/draft-ietf-oauth-security-topics-16