default_namespace on SHC

clayraed — Fri, 10 Nov 2023 20:08:35 GMT

I have created an app for a team that I work with, and have set up mapping from our SAML auth so that the people on the team get a role that has access to the app.

I would like for when these folks log in (they only have this one role, no other roles -- not even the default user role), they would land on the home page for the app. As I understand it, that's supposed to be accomplished with the default_namespace parameter, set in the $SPLUNK_HOME/etc/apps/user-prefs/local/user-prefs.conf.

In a regular browser window, now, when they log in, they get a 404 page for the app's home page (en-US/app/<appname>/search). If they do it in an incognito/private browsing window, they land on the Launcher app and then then can navigate to the app and it works just fine. The app's home page exists and is absolutely NOT a 404; after logging in in incognito, the URL they get when they manually navigate to the app is identical to the the link they're landed on when logging in without incognito. (Ideally, I don't want these users to have access to the Launcher app, even. But for now, they have to, in order to work around this.)

We have a distributed environment (multiple indexers, multiple load-balanced search heads with a VIP). This is the first time I've worked in a distributed environment. So I'm assuming it's something to do with that.

Any tips on what I'm doing wrong?

topic default_namespace on SHC in Deployment Architecture

default_namespace on SHC