<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rbac on ErrorVault — Developer Error Code Dictionary</title>
    <link>https://errorvault.dev/tags/rbac/</link>
    <description>Recent content in Rbac on ErrorVault — Developer Error Code Dictionary</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 12 Aug 2026 03:08:04 +0800</lastBuildDate>
    <atom:link href="https://errorvault.dev/tags/rbac/feed.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Fix clw-api-denied: OpenClaw API Request Denied Error</title>
      <link>https://errorvault.dev/openclaw/openclaw-clw-api-denied-error/</link>
      <pubDate>Wed, 12 Aug 2026 03:08:04 +0800</pubDate>
      <guid>https://errorvault.dev/openclaw/openclaw-clw-api-denied-error/</guid>
      <description>&lt;h1 id=&#34;fix-clw-api-denied-openclaw-api-request-denied-error&#34;&gt;Fix clw-api-denied: OpenClaw API Request Denied Error&lt;/h1&gt;&#xA;&lt;p&gt;The &lt;code&gt;clw-api-denied&lt;/code&gt; error is a critical authorization failure that occurs when the OpenClaw API rejects a request because the client lacks the necessary permissions or scope to perform the requested operation. This error typically manifests as an HTTP 403 Forbidden response and indicates a deliberate access control decision made by the OpenClaw authorization layer. Understanding the intricacies of this error is essential for developers and system administrators who are building, deploying, or maintaining applications that interact with OpenClaw&amp;rsquo;s API infrastructure.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Fix clw-worker-denied: Worker Access Denied by Cluster Security Policy</title>
      <link>https://errorvault.dev/openclaw/openclaw-clw-worker-denied-worker-access-denied/</link>
      <pubDate>Thu, 21 May 2026 00:44:04 +0800</pubDate>
      <guid>https://errorvault.dev/openclaw/openclaw-clw-worker-denied-worker-access-denied/</guid>
      <description>&lt;h2 id=&#34;1-symptoms&#34;&gt;1. Symptoms&lt;/h2&gt;&#xA;&lt;p&gt;When the &lt;code&gt;clw-worker-denied&lt;/code&gt; error occurs, users typically observe the following symptoms:&lt;/p&gt;&#xA;&lt;p&gt;&lt;strong&gt;In the OpenClaw Dashboard:&lt;/strong&gt;&lt;/p&gt;&#xA;&lt;ul&gt;&#xA;&lt;li&gt;Worker status shows as &lt;code&gt;REJECTED&lt;/code&gt; instead of &lt;code&gt;READY&lt;/code&gt;&lt;/li&gt;&#xA;&lt;li&gt;Task queue displays workers but marks them with a red deny icon&lt;/li&gt;&#xA;&lt;li&gt;Jobs remain in &lt;code&gt;PENDING&lt;/code&gt; state without worker assignment&lt;/li&gt;&#xA;&lt;/ul&gt;&#xA;&lt;h2 id=&#34;in-the-worker-logs&#34;&gt;&lt;strong&gt;In the Worker Logs:&lt;/strong&gt;&lt;/h2&gt;&#xA;&lt;p&gt;[2025-01-15 10:42:18] INFO  Connecting to cluster at &lt;a href=&#34;https://cluster.openclaw.io&#34;&gt;https://cluster.openclaw.io&lt;/a&gt;&#xA;[2025-01-15 10:42:19] ERROR clw-worker-denied: Worker registration rejected by cluster security policy&#xA;[2025-01-15 10:42:19] ERROR Reason: Worker identity does not match allowed patterns for namespace &amp;lsquo;production&amp;rsquo;&#xA;[2025-01-15 10:42:19] INFO  Retrying in 30 seconds&amp;hellip;&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
