OAuth 2.0 Dynamic Client Registration: RFC 7591, 7592
Whether you’re building a massive SaaS platform or a niche API, OAuth is the gold standard for authorization. In such there might arise a hurdle that every developer faces: Registration.
Whether you’re building a massive SaaS platform or a niche API, OAuth is the gold standard for authorization. In such there might arise a hurdle that every developer faces: Registration.
Everyone mostly understands the OIDC login flow correct. It’s simple and staight-forward, you do the authorization code flow, validate the ID Token, set a session cookie, and done. Logout is where things becomes a bit complex and they usually happen silently.
This is part 2 of nuts and bolts of OAuth 2.0, continuing part 1. In this section, I’ll explore the client credentials flow for machine-to-machine communication
In this blog, I want to summarize whatever I learned from the nuts and bolts of OAuth 2.0 by Aaron Parecki’s Udemy course. This was one of the nicest things I have done when starting to learn OAuth myself (and I surely recommend this).