Splunk ITSI

ITSI "suite_redirect" page fails to load with shows "oops" for non admin users

yannK
Splunk Employee
Splunk Employee
 
ITSI menus send the users to "suite_redirect" page, that also fails to load with shows "oops" for non admin users Usually after an ITSI Upgrade (observed on 4.9 and later), on a Search-Head cluster.
Labels (2)
0 Karma
1 Solution

yannK
Splunk Employee
Splunk Employee

see known bug ITSI-20605

Check the roles: are all the users impacted or are only non-admin roles impacted?
Check the web_service.log in index=_internal, do you see errors like that or different views or management views.

 

An unknown view name "homeview" is referenced in the navigation definition for "itsi".

 



Check the app metadata permissions for those views.
Example: in ../etc/apps/itsi/metadata/local.meta, look for the view "homeview"
Check which roles have read and write permissions, If only the admin can, there it's the root cause.
Compare to the default permissions in ../etc/apps/itsi/metadata/default.meta

A corrupted permissions stanza will look like that, you see no roles in the brackets :

 

 

access = delete : [ ], read : [ ], write : [ ]

 

 

 

Resolution

Clean the .../etc/apps/itsi/metadata/local.meta
Removed all stanzas impacted, as they were conflicting with the definition is default.meta
If the instance is a Search-head cluster, you will have to fix is on all Search Head, and restart.

View solution in original post

0 Karma

yannK
Splunk Employee
Splunk Employee

see known bug ITSI-20605

Check the roles: are all the users impacted or are only non-admin roles impacted?
Check the web_service.log in index=_internal, do you see errors like that or different views or management views.

 

An unknown view name "homeview" is referenced in the navigation definition for "itsi".

 



Check the app metadata permissions for those views.
Example: in ../etc/apps/itsi/metadata/local.meta, look for the view "homeview"
Check which roles have read and write permissions, If only the admin can, there it's the root cause.
Compare to the default permissions in ../etc/apps/itsi/metadata/default.meta

A corrupted permissions stanza will look like that, you see no roles in the brackets :

 

 

access = delete : [ ], read : [ ], write : [ ]

 

 

 

Resolution

Clean the .../etc/apps/itsi/metadata/local.meta
Removed all stanzas impacted, as they were conflicting with the definition is default.meta
If the instance is a Search-head cluster, you will have to fix is on all Search Head, and restart.

0 Karma
Get Updates on the Splunk Community!

Developer Spotlight with Paul Stout

Welcome to our very first developer spotlight release series where we'll feature some awesome Splunk ...

State of Splunk Careers 2024: Maximizing Career Outcomes and the Continued Value of ...

For the past four years, Splunk has partnered with Enterprise Strategy Group to conduct a survey that gauges ...

Data-Driven Success: Splunk & Financial Services

Splunk streamlines the process of extracting insights from large volumes of data. In this fast-paced world, ...