3 years ago

Category: Database, Kubernetes, github, yaml

Understanding OAuth2, OpenID and OpenID Connect (OIDC), how they relate, how the communications are established, and how to architecture your application with the given access, refresh and id tokens is confusing. There was a time when securing your application was not so complicated to implement.

Part 1, OAuth2 and OpenID Connect, a gentle and working introduction focuses on integrating your first application with an OpenID Connect server (Dex) and experienced the Authorization Code Flow with an external provider.

The OAuth server, which is also the OpenID Connect server, is called the Authorization Server (AS) and it is in charge of issuing the tokens and determine who the end-user is.

If you are interested in how to use it with a public client application, read the follow-up article, OAuth2 and OpenID Connect for microservices and public applications (Part 2).