<?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: Inability to delete alerts/reports after LDAP update in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Inability-to-delete-alerts-reports-after-LDAP-update/m-p/700113#M237602</link>
    <description>&lt;P&gt;If you have a search head cluster on prem try electing a new captain to force push a new SHC bundle.&lt;/P&gt;&lt;P&gt;If that doesn't work then more information would be required about how user and roles are working and if you have any thing has changed there.&amp;nbsp; Is there anything via auth .conf doesn't show up anymore.&lt;/P&gt;</description>
    <pubDate>Wed, 25 Sep 2024 16:04:15 GMT</pubDate>
    <dc:creator>dural_yyz</dc:creator>
    <dc:date>2024-09-25T16:04:15Z</dc:date>
    <item>
      <title>Inability to delete alerts/reports after LDAP update</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Inability-to-delete-alerts-reports-after-LDAP-update/m-p/699977#M237575</link>
      <description>&lt;P&gt;Hello,&lt;BR /&gt;I recently updated a distributed environment with a bundle via the deployer to update the authentication.conf to have an updated LDAP strategy.&amp;nbsp; Since then there have been a number of issue with users not being able to delete their knowledge objects which prompted me to try as my Admin user. However this is the error I am receiving when trying to delete via the web ui:&lt;BR /&gt;&lt;BR /&gt;09-24-2024 16:52:13.948 +0000 ERROR SavedSearchAdminHandler [2802356 TcpChannelThread] - This saved search failed to handle removal request due to Object id=&amp;lt;alert/report name&amp;gt; cannot be deleted in config=savedsearches.&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;I am using Splunk Enterprise version 9.3.0.&lt;/P&gt;</description>
      <pubDate>Tue, 24 Sep 2024 16:58:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Inability-to-delete-alerts-reports-after-LDAP-update/m-p/699977#M237575</guid>
      <dc:creator>Reece</dc:creator>
      <dc:date>2024-09-24T16:58:57Z</dc:date>
    </item>
    <item>
      <title>Re: Inability to delete alerts/reports after LDAP update</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Inability-to-delete-alerts-reports-after-LDAP-update/m-p/700113#M237602</link>
      <description>&lt;P&gt;If you have a search head cluster on prem try electing a new captain to force push a new SHC bundle.&lt;/P&gt;&lt;P&gt;If that doesn't work then more information would be required about how user and roles are working and if you have any thing has changed there.&amp;nbsp; Is there anything via auth .conf doesn't show up anymore.&lt;/P&gt;</description>
      <pubDate>Wed, 25 Sep 2024 16:04:15 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Inability-to-delete-alerts-reports-after-LDAP-update/m-p/700113#M237602</guid>
      <dc:creator>dural_yyz</dc:creator>
      <dc:date>2024-09-25T16:04:15Z</dc:date>
    </item>
    <item>
      <title>Re: Inability to delete alerts/reports after LDAP update</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Inability-to-delete-alerts-reports-after-LDAP-update/m-p/700216#M237640</link>
      <description>&lt;P&gt;I have elected a new captain in my SH cluster a few times over the course of a couple days to see if there was some type of connection issue b/w specific SHs but still presenting same error. The only changes in auth.conf were the ldap servers, the hosts, the groupings and permissions are all identical.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 26 Sep 2024 13:21:57 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Inability-to-delete-alerts-reports-after-LDAP-update/m-p/700216#M237640</guid>
      <dc:creator>Reece</dc:creator>
      <dc:date>2024-09-26T13:21:57Z</dc:date>
    </item>
  </channel>
</rss>

