<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Keycloak on Rework-Space</title>
    <link>https://rework-space.com/blog_tags/keycloak/</link>
    <description>Recent content in Keycloak on Rework-Space</description>
    <generator>Hugo -- gohugo.io</generator>
    <language>en</language>
    <lastBuildDate>Fri, 27 Mar 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://rework-space.com/blog_tags/keycloak/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Keycloak Fine-Grained Admin Permissions (FGAP) V2: Fine-Grained Access &amp; Safe Impersonation</title>
      <link>https://rework-space.com/blog/2026-03-27-keycloak-fine-grained-admin-permissions-v2/</link>
      <pubDate>Fri, 27 Mar 2026 00:00:00 +0000</pubDate>
      
      <guid>https://rework-space.com/blog/2026-03-27-keycloak-fine-grained-admin-permissions-v2/</guid>
      <description>The problem Basic Keycloak permissions can be granted via the roles present in system clients. The realm-management client is used in most cases. However, there is a problem: existing permissions cannot be configured to meet your needs and provide too much access. You can make a user to manage all users in the realm or manage no one.
There are two possible scenarios in this case. Only a limited number of developers have access to the realm, which makes them responsible for managing test users.</description>
    </item>
    
  </channel>
</rss>
