Security

Navigation Menu Default.xml Default View Cascading for Permission Restricted View

fsolercasanova
Explorer

What is the expected behavior for setting multiple default views in the default.xml navigation menu?

<nav search_view="search">
    <collection label="DefaultViews">
        <view name="permission_restricted_d1" default='true' />
        <view name="unrestricted_d2" default='true' />
 </collection>

The documentation has a case where multiple defaults are set in the same app and collection implying some sort of expected behavior.

In practice, restricting a users access to permisson_restricted_d1 causes a 404 error and does not cascade to unrestricted_d2.

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?

0 Karma
Get Updates on the Splunk Community!

Splunk Enterprise Security: Your Command Center for PCI DSS Compliance

Every security professional knows the drill. The PCI DSS audit is approaching, and suddenly everyone's asking ...

Developer Spotlight with Guilhem Marchand

From Splunk Engineer to Founder: The Journey Behind TrackMe    After spending over 12 years working full time ...

Cisco Catalyst Center Meets Splunk ITSI: From 'Payments Are Down' to Root Cause in ...

The Problem: When Networks and Services Don't Talk Payment systems fail at a retail location. Customers are ...