
		<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
			<channel>
				<title>Hameed Syed K · Product, Identity &amp; Agentic AI</title>
				<link>https://www.shkcorp.com/blog</link>
				<description>Notes from a technical product leader on product management, identity &amp; access management, and agentic AI — from 12 years of building enterprise software.</description>
				<language>en-us</language>
				<managingEditor>kshameed7@gmail.com (Hameed Syed K)</managingEditor>
				<webMaster>kshameed7@gmail.com (Hameed Syed K)</webMaster>
				<lastBuildDate>Mon, 02 Nov 2026 00:00:00 GMT</lastBuildDate>
				<atom:link href="https://www.shkcorp.com/tags/jwks/feed.xml" rel="self" type="application/rss+xml"/>
				
		<item>
			<guid>https://www.shkcorp.com/blog/iam-chapter-5-part-3-oidc-who-logged-in</guid>
			<title>IAM Chapter 5, Part 3: Who Logged In</title>
			<link>https://www.shkcorp.com/blog/iam-chapter-5-part-3-oidc-who-logged-in</link>
			<description>OAuth got the app permission. It never said whose permission it was. OpenID Connect adds the ID token, the four checks that make it worth anything, published signing keys, and discovery: one string instead of four.</description>
			<pubDate>Mon, 02 Nov 2026 00:00:00 GMT</pubDate>
			<author>kshameed7@gmail.com (Hameed Syed K)</author>
			<category>iam</category><category>oidc</category><category>openid-connect</category><category>oauth</category><category>jwt</category><category>jwks</category><category>security</category><category>study-notes</category>
		</item>
	
			</channel>
		</rss>
	