<?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 Navigation Menu Default.xml Default View Cascading for Permission Restricted View in Security</title>
    <link>https://community.splunk.com/t5/Security/Navigation-Menu-Default-xml-Default-View-Cascading-for/m-p/456695#M10658</link>
    <description>&lt;P&gt;What is the expected behavior for setting multiple default views in the default.xml navigation menu?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;nav search_view="search"&amp;gt;
    &amp;lt;collection label="DefaultViews"&amp;gt;
        &amp;lt;view name="permission_restricted_d1" default='true' /&amp;gt;
        &amp;lt;view name="unrestricted_d2" default='true' /&amp;gt;
 &amp;lt;/collection&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The &lt;A href="https://docs.splunk.com/Documentation/Splunk/6.4.11/AdvancedDev/BuildNavigation#Dynamically_include_all_views" target="_blank"&gt;documentation&lt;/A&gt; has a case where multiple defaults are set in the same app and collection implying some sort of expected behavior.&lt;/P&gt;

&lt;P&gt;In practice, restricting a users access to permisson_restricted_d1 causes a 404 error and does not cascade to unrestricted_d2.&lt;/P&gt;

&lt;P&gt;Is this a known issue and/or is there a workaround available that would not involve creating a new app with alternate navigation to the same resources?&lt;/P&gt;</description>
    <pubDate>Wed, 30 Sep 2020 01:49:53 GMT</pubDate>
    <dc:creator>fsolercasanova</dc:creator>
    <dc:date>2020-09-30T01:49:53Z</dc:date>
    <item>
      <title>Navigation Menu Default.xml Default View Cascading for Permission Restricted View</title>
      <link>https://community.splunk.com/t5/Security/Navigation-Menu-Default-xml-Default-View-Cascading-for/m-p/456695#M10658</link>
      <description>&lt;P&gt;What is the expected behavior for setting multiple default views in the default.xml navigation menu?&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;&amp;lt;nav search_view="search"&amp;gt;
    &amp;lt;collection label="DefaultViews"&amp;gt;
        &amp;lt;view name="permission_restricted_d1" default='true' /&amp;gt;
        &amp;lt;view name="unrestricted_d2" default='true' /&amp;gt;
 &amp;lt;/collection&amp;gt;
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;The &lt;A href="https://docs.splunk.com/Documentation/Splunk/6.4.11/AdvancedDev/BuildNavigation#Dynamically_include_all_views" target="_blank"&gt;documentation&lt;/A&gt; has a case where multiple defaults are set in the same app and collection implying some sort of expected behavior.&lt;/P&gt;

&lt;P&gt;In practice, restricting a users access to permisson_restricted_d1 causes a 404 error and does not cascade to unrestricted_d2.&lt;/P&gt;

&lt;P&gt;Is this a known issue and/or is there a workaround available that would not involve creating a new app with alternate navigation to the same resources?&lt;/P&gt;</description>
      <pubDate>Wed, 30 Sep 2020 01:49:53 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/Navigation-Menu-Default-xml-Default-View-Cascading-for/m-p/456695#M10658</guid>
      <dc:creator>fsolercasanova</dc:creator>
      <dc:date>2020-09-30T01:49:53Z</dc:date>
    </item>
  </channel>
</rss>

