<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Identity Management on zar3bski</title>
    <link>https://zar3bski.com/tags/identity-management/</link>
    <description>Recent content in Identity Management on zar3bski</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <copyright>© [David Zarebski](https://zar3bski.com) </copyright>
    <lastBuildDate>Fri, 13 Nov 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://zar3bski.com/tags/identity-management/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Realm based RBAC in Keycloak</title>
      <link>https://zar3bski.com/devops/keycloak_rbac/</link>
      <pubDate>Fri, 13 Nov 2026 00:00:00 +0000</pubDate>
      <guid>https://zar3bski.com/devops/keycloak_rbac/</guid>
      <description>&lt;h2 id=&#34;the-need&#34;&gt;The need&lt;/h2&gt;&#xA;&lt;p&gt;As an identity server, the main purpose of Keycloak is to provide single authentication methods for many applications while leaving the task&#xA;of filtering users access to the later based on custom, application side, claims to role mappings. In short, Keycloak provides authentication and identification while the application servers handle &lt;strong&gt;Role Based Access Control&lt;/strong&gt; (&lt;strong&gt;RBAC&lt;/strong&gt;) based on the claims retrieved from the identity server. Such distribution of responsibility allows fine-grained access-control.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
