Archive
Highlighted

Cannot get list of apps in Splunk Mobile App (Splunk Add-on for Mobile Access installed and configured)

Builder

Hi all,

We've installed Splunk Add-on for Mobile Access, checked its configurations (http://docs.splunk.com/Documentation/MobileAddon/latest/Install/Configuredisplay), installed Splunk iOS app, logined with SSO, but see no our apps, though by default all of them enabled for mobile access.
In logs nothing suspicious.
What can be the problem?

UPDATE
That was on iOS app. Installed Android app and it displayed my app! With savedsearches but without dashboards in it.

0 Karma
Highlighted

Re: Cannot get list of apps in Splunk Mobile App (Splunk Add-on for Mobile Access installed and configured)

Path Finder

Hi What kind of SSO do you use? It looks like that it's a complicated case. It can not be solved in a few words.
If possible, could you please send a mail to mobile-support@splunk.com, and copy paste the above question so that we can ask you learn more about the network topologic, SSO type, and other info by mails? Thanks

0 Karma
Highlighted

Re: Cannot get list of apps in Splunk Mobile App (Splunk Add-on for Mobile Access installed and configured)

Builder

Hi Roy, is it correct email address? I didn't manage to send message to mobile-support@splunk.com, then I tried several variants and seems that your meant mobilesupport@splunk.com. Or did I send email to someone else?))

Highlighted

Re: Cannot get list of apps in Splunk Mobile App (Splunk Add-on for Mobile Access installed and configured)

Path Finder

Sorry, it should be mobileaccess-support@splunk.com

0 Karma
Highlighted

Re: Cannot get list of apps in Splunk Mobile App (Splunk Add-on for Mobile Access installed and configured)

Builder

We’ve managed to solve the problem with iOS app) Just in case someone will face the same problem:
After checking TCP-dump again we’ve discovered that while SSO-login client sends port number in the header. Normally it is stated if it’s unusual but here it was added always. And our Netscaler had a rule with strict matching HEADER.HOST.EQ("server.name") that caused ignoring of request unless we’ve stated server.name:80 and 443
Now it is up and running)

View solution in original post

0 Karma
Speak Up for Splunk Careers!

We want to better understand the impact Splunk experience and expertise has has on individuals' careers, and help highlight the growing demand for Splunk skills.