Troubleshoot SAML Authentication with the Connected Experiences apps
If you're encountering issues with Security Assertion Markup Language (SAML) for your Connected Experiences apps, see the following troubleshooting tips.
Unable to register device
If you receive an error message when attempting to register your device, see the following possible causes and workarounds. The error codes appear in Splunk Mobile for Android but do not appear in Splunk Mobile for iOS. Use the same troubleshooting steps for Splunk Mobile for iOS if you encounter a registration error.
|Error Code||Possible cause||Workaround|
|MOB-DEV-310||There's a network connection error.||Make sure you have a network connection, check if you need to be connected to a VPN, and make sure the Splunk platform instance that you're connecting to is active.|
|MOB-SSG-400||There's an issue with Splunk Secure Gateway or Spacebridge.||Troubleshoot Splunk Secure Gateway. See Troubleshoot Splunk Secure Gateway connection issues and Troubleshoot Splunk Secure Gateway performance issues.|
|MOB-SSG-404||The authentication code has expired.||If you selected Register with Code, the authentication code expires in 15 minutes. Enter the refreshed authentication code.|
|MOB-SSG-409||Device name already exists.||Enter a different device name.|
|MOB-SSG-422||Splunk Secure Gateway is unable to generate a token for the device with SAML authentication.||Make sure you've configured SAML authentication correctly. See Set up SAML authentication for Splunk Secure Gateway.|
|MOB-SSG-500||There's an internal Spacebridge error.||Contact your Splunk admin.|
|MOB-SSG-503||There's an internal Spacebridge error.||Contact your Splunk admin.|
How devices authenticate to your Splunk platform with SAML authentication
About MDM and in-app registration
This documentation applies to the following versions of Splunk® Secure Gateway: 2.4.0, 2.5.7, 2.7.4, 2.9.1 Cloud only, 2.9.3 Cloud only, 2.9.4 Cloud only