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

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

iKate — Thu, 23 Jun 2016 16:22:32 GMT

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.

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

roym_splunk — Tue, 28 Jun 2016 08:03:38 GMT

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

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

iKate — Tue, 28 Jun 2016 14:14:52 GMT

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?))

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

roym_splunk — Wed, 29 Jun 2016 02:24:56 GMT

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

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

iKate — Mon, 04 Jul 2016 13:02:43 GMT

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)