<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Sso on Le Site de François</title><link>https://lesitedefrancois.be/en/tags/sso/</link><description>Recent content in Sso on Le Site de François</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 François</copyright><atom:link href="https://lesitedefrancois.be/en/tags/sso/index.xml" rel="self" type="application/rss+xml"/><item><title>OIDC (OpenID Connect)</title><link>https://lesitedefrancois.be/en/security/oidc/</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://lesitedefrancois.be/en/security/oidc/</guid><description>&lt;p&gt;&lt;strong&gt;OpenID Connect (OIDC)&lt;/strong&gt; is an authentication protocol built as a thin layer on top of &lt;strong&gt;OAuth 2.0&lt;/strong&gt;, published by the OpenID Foundation in 2014. Where OAuth 2.0 defines how to delegate authorisation (granting access to resources), OIDC adds the missing authentication semantics: a standard &lt;strong&gt;ID token&lt;/strong&gt; that proves who the user is, a &lt;strong&gt;UserInfo endpoint&lt;/strong&gt; that returns standardised identity claims, and a &lt;strong&gt;discovery document&lt;/strong&gt; that allows clients to configure themselves automatically from a single well-known URL. The separation is precise: OAuth 2.0 access tokens prove that a client is authorised to call an API; OIDC ID tokens prove that a specific user authenticated with a specific identity provider at a specific time. OIDC is the protocol behind virtually every &amp;ldquo;Sign in with Google / GitHub / Microsoft&amp;rdquo; flow, every SAML-to-modern-stack migration, and every Kubernetes service account token issued today — making it the dominant authentication federation standard in cloud-native infrastructure.&lt;/p&gt;</description></item></channel></rss>