<?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 Private KO Access Post SAML Implimentation in Security</title>
    <link>https://community.splunk.com/t5/Security/Private-KO-Access-Post-SAML-Implimentation/m-p/535206#M12034</link>
    <description>&lt;P&gt;What happens to privately owned knowledge objects when the Splunk authentication method is switched from Native Splunk Enterprise authentication to SAML?&amp;nbsp; If the logon names are the same, will users be able to access their private KO created before the switch?&lt;/P&gt;</description>
    <pubDate>Fri, 08 Jan 2021 14:51:24 GMT</pubDate>
    <dc:creator>Ed11375</dc:creator>
    <dc:date>2021-01-08T14:51:24Z</dc:date>
    <item>
      <title>Private KO Access Post SAML Implimentation</title>
      <link>https://community.splunk.com/t5/Security/Private-KO-Access-Post-SAML-Implimentation/m-p/535206#M12034</link>
      <description>&lt;P&gt;What happens to privately owned knowledge objects when the Splunk authentication method is switched from Native Splunk Enterprise authentication to SAML?&amp;nbsp; If the logon names are the same, will users be able to access their private KO created before the switch?&lt;/P&gt;</description>
      <pubDate>Fri, 08 Jan 2021 14:51:24 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Private-KO-Access-Post-SAML-Implimentation/m-p/535206#M12034</guid>
      <dc:creator>Ed11375</dc:creator>
      <dc:date>2021-01-08T14:51:24Z</dc:date>
    </item>
  </channel>
</rss>

