The OpenID Connect (OIDC) Architecture Map
Published Jan 21 2020 01:51 AM 12.1K Views



Yet another map! This map is part of my series of Architecture Maps:


This time it is not Azure specific, although the map has some touch points with Azure Active Directory v1 and Microsoft Identity Platform (v2 endpooints).  During my consulting activities, I have realized that OAuth 2.0 and even more OIDC remain quite largely unknown or misunderstood. This map is aimed at describing the OIDC landscape (flows, endpoints, etc.) and when to use what. It is a high level representation including some remarks.


As usual, this map is by no means the holy grail and is just there to highlight some key areas to look at when starting a modern authentication journey. It is also not related to a specific Identity Provider.

As usual, here is a screenshot of the map:The OIDC Map.png


The map focuses on the following areas:

  • Endpoints
  • Flows
  • Token Types
  • Channels
  • Authorization aspects

How to read this map?


Whenever you see the attachment icon attachicon.png, it means that I have attached an explanation on a given rationale or service. If you see this iconattention.png next to a node, it means that I have attached a must-read information.


Here is the pointer to the map:

v1.0 (01/2020)


Here are all my Architecture Maps:

Version history
Last update:
‎Mar 27 2020 01:46 PM
Updated by: