Hello, I created a Splunk app with 4 dashboards and i configured the app navigation bar to only show those 4 dashboards. <nav>
<view name="dashboard_1"/>
<view name="dashboard_2"/>
<view name="dashboard_3"/>
<view name="dashboard_4"/>
</nav> However, the user permissions for each one of them are different depending on the user's role. There are users that can only see DASHBOARD_1, others can only see DASHBOARD_2, some can see both DASHBOARD_2 and DASHBOARD_3, among a series of other combinations... My problem is with the users that can only view dashboards 2, 3 and 4, because even though they explicitly DO NOT have permissions to view DASHBOARD_1, when they enter the App, Splunk always tries to open that one. As you can imagine the result is an error page with the horse and the "Oops.". I understand that because it is the first one in the navigation bar, Splunk assumes it's the homepage of that app. But I also expected Splunk to take the user permissions into consideration. Meaning that if a certain user only has permissions to see dashboards 3 and 4, the App navigation bar should only show those 2 options and when they open the App, it should open on DASHBOARD_3. This was working great a few months back and at some point it just stopped - I can't be precise on when exactly that happened . I managed to find a workaround by replacing all the <view> entries shown above with: <nav>
<view source="all" match="dashboard_1"/>
<view source="all" match="dashboard_2"/>
<view source="all" match="dashboard_3"/>
<view source="all" match="dashboard_4"/>
</nav> However, a few days ago Splunk was updated from version 9.0.2 to 9.2.1 and the workaround stopped working as well. I'm sure I'm missing something. What can I do so that Splunk obeys the dashboards user permissions in this situation and doesn't redirect the user to a dashboard they don't even have permission to view? Thank you.
... View more