Splunk IT Service Intelligence

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!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...