<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: debug/refresh for authorize.conf capabilities in Security</title>
    <link>https://community.splunk.com/t5/Security/debug-refresh-for-authorize-conf-capabilities/m-p/695047#M18052</link>
    <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/263556"&gt;@marnall&lt;/a&gt;&amp;nbsp;thanks however this is not clear from support side, I've already been asked to only do debug/refresh for capabilities.&lt;/P&gt;</description>
    <pubDate>Fri, 02 Aug 2024 07:33:16 GMT</pubDate>
    <dc:creator>splunkreal</dc:creator>
    <dc:date>2024-08-02T07:33:16Z</dc:date>
    <item>
      <title>debug/refresh for authorize.conf capabilities</title>
      <link>https://community.splunk.com/t5/Security/debug-refresh-for-authorize-conf-capabilities/m-p/695019#M18050</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;Is /debug/refresh enough to reload role capabilities for authorize.conf?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Splunk entreprise v9&lt;/P&gt;</description>
      <pubDate>Thu, 01 Aug 2024 18:49:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/debug-refresh-for-authorize-conf-capabilities/m-p/695019#M18050</guid>
      <dc:creator>splunkreal</dc:creator>
      <dc:date>2024-08-01T18:49:24Z</dc:date>
    </item>
    <item>
      <title>Re: debug/refresh for authorize.conf capabilities</title>
      <link>https://community.splunk.com/t5/Security/debug-refresh-for-authorize-conf-capabilities/m-p/695024#M18051</link>
      <description>&lt;P&gt;Not by default, as that would log out active sessions in the web UI.&lt;/P&gt;&lt;P&gt;You can trigger a refresh of the auth-services endpoint by specifying it as an entity. I think this will reload authorize.conf but I have not tested it.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;/debug/refresh?entity=admin/auth-services&lt;/LI-CODE&gt;</description>
      <pubDate>Thu, 01 Aug 2024 20:13:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/debug-refresh-for-authorize-conf-capabilities/m-p/695024#M18051</guid>
      <dc:creator>marnall</dc:creator>
      <dc:date>2024-08-01T20:13:51Z</dc:date>
    </item>
    <item>
      <title>Re: debug/refresh for authorize.conf capabilities</title>
      <link>https://community.splunk.com/t5/Security/debug-refresh-for-authorize-conf-capabilities/m-p/695047#M18052</link>
      <description>&lt;P&gt;Hello&amp;nbsp;&lt;a href="https://community.splunk.com/t5/user/viewprofilepage/user-id/263556"&gt;@marnall&lt;/a&gt;&amp;nbsp;thanks however this is not clear from support side, I've already been asked to only do debug/refresh for capabilities.&lt;/P&gt;</description>
      <pubDate>Fri, 02 Aug 2024 07:33:16 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/debug-refresh-for-authorize-conf-capabilities/m-p/695047#M18052</guid>
      <dc:creator>splunkreal</dc:creator>
      <dc:date>2024-08-02T07:33:16Z</dc:date>
    </item>
    <item>
      <title>Re: debug/refresh for authorize.conf capabilities</title>
      <link>https://community.splunk.com/t5/Security/debug-refresh-for-authorize-conf-capabilities/m-p/695231#M18056</link>
      <description>&lt;P&gt;Hello, looks like debug/refresh was enough.&lt;/P&gt;</description>
      <pubDate>Mon, 05 Aug 2024 10:11:29 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/debug-refresh-for-authorize-conf-capabilities/m-p/695231#M18056</guid>
      <dc:creator>splunkreal</dc:creator>
      <dc:date>2024-08-05T10:11:29Z</dc:date>
    </item>
  </channel>
</rss>

