<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>InfoQ - Java - Articles</title>
    <link>https://www.infoq.com</link>
    <description>InfoQ Java Articles feed</description>
    <item>
      <title>Article: Identity as an Architectural Concern: Enterprise IAM Beyond Authentication</title>
      <link>https://www.infoq.com/articles/identity-as-architecture/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Java-articles</link>
      <description>&lt;img src="https://res.infoq.com/articles/identity-as-architecture/en/headerimage/identity-as-architecture-header-1793629959196.jpg"/&gt;&lt;p&gt;The way you design your identities will drive your data models, your service scope, and your revocation policies; enterprise identity management is thus an architectural problem, not an afterthought. Based on our experience in service account governance, this article touches upon graph vs. RBAC, integrating a vault you don't own, and bounding revocation latency for an event stream.&lt;/p&gt; &lt;i&gt;By Vaishnavi Khosla&lt;/i&gt;</description>
      <category>Java</category>
      <category>Single Sign-On</category>
      <category>Architecture</category>
      <category>OAuth</category>
      <category>Identity Management</category>
      <category>Development</category>
      <category>Architecture &amp; Design</category>
      <category>article</category>
      <pubDate>Fri, 06 Nov 2026 09:00:00 GMT</pubDate>
      <guid>https://www.infoq.com/articles/identity-as-architecture/?utm_campaign=infoq_content&amp;utm_source=infoq&amp;utm_medium=feed&amp;utm_term=Java-articles</guid>
      <dc:creator>Vaishnavi Khosla</dc:creator>
      <dc:date>2026-11-06T09:00:00Z</dc:date>
      <dc:identifier>/articles/identity-as-architecture/en</dc:identifier>
    </item>
  </channel>
</rss>
