Hi all,
Here I am with another article that can get you a little bit higher on your IAM ladder. In my previous articles, I talked about what OAuth is, it’s grant types and what OpenID Connect is. Today I intend to give you hands-on experience with a real-life OAuth and OIDC implementation that is used by more than 100 companies around the world, and it’s the WSO2 Identity Server’s OAuth/OIDC implementation.
Hello everyone!
In my previous posts, I talked about the basic OAuth concept (IAM for dummies: How does OAuth work) and OAuth Grant types (IAM for dummies: OAuth 2 Grant Types). Today, I’m going to give you an understanding of OpenID Connect.
I talked about the concept of OAuth in my previous post. Today I’m going to dive a bit too deep and talk about the implementation details provided by the OAuth 2.0 specification. The first specific of OAuth was OAuth 1.0 and after a few years of the use, people identified some problems with it and created OAuth 2.0, the improved version.
What’s up, guys?
Today I’m going to talk about OAuth. I’ve been delivering OAuth presentations for a while now and I can’t believe it didn’t cross my mind to write something up on it. So here goes nothing!
OAuth is THE industry-standard protocol for authorization. It is used by a majority of software service providers including WSO2 Identity Server, which is known for it’s fully functional OAuth features as an Identity Provider. OK, cool. Why should I care? Well, let me give you a practical real-life example of OAuth before going into details.
everything I know 