<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Splunk Secure Gateway connection error in Splunk Enterprise</title>
    <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Secure-Gateway-connection-error/m-p/596995#M12484</link>
    <description>&lt;P&gt;We are having a connection issue on Splunk Enterprise 8.2.6 on prem with Splunk Secure Gateway 2.7.4, according to the firewall rules the connection port 443 outbound to the host prod.spacebridge.spl.mobi is allowed.&lt;BR /&gt;&lt;BR /&gt;We verified the connection using the troubleshooting guide in the documentation by running:&lt;/P&gt;&lt;PRE&gt;curl https://prod.spacebridge.spl.mobi/health_check&lt;/PRE&gt;&lt;P&gt;Also we tried the test for wss connection and we get the correct response:&lt;/P&gt;&lt;PRE&gt;curl -i -N -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Host: echo.websocket.events" -H "Origin: https://echo.websocket.events" -H "Sec-WebSocket-Key: d3d3LnNwbHVuay5jb20=" -H "Sec-WebSocket-Version: 13" https://echo.websocket.events&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;When we run the following rest command:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rest "services/ssg/test_websocket" request_type="{\"versionGetRequest\": {}}" request_mode=clientSingleRequest&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We get this output:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;auth_code_status = 200
completed_client_registration = 0
error = 'token_id'
server_registration_status = 400
splunk_server = server
wss_response = 0&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The error traceback in _internal is:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;2022-05-09 11:22:58,148 ERROR [rest_base] [__init__] [exception] [4772] Spacebridge error
Traceback (most recent call last):
  File "/opt/splunk/etc/apps/splunk_secure_gateway/bin/spacebridgeapp/rest/util/helper.py", line 13, in extract_parameter
    result = obj[key]
KeyError: 'self_register'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/opt/splunk/etc/apps/splunk_secure_gateway/bin/spacebridgeapp/rest/base_endpoint.py", line 53, in handle
    res = self.handle_request(request)
  File "/opt/splunk/etc/apps/splunk_secure_gateway/bin/spacebridgeapp/rest/base_endpoint.py", line 86, in handle_request
    return self.post(request)
  File "/opt/splunk/etc/apps/splunk_secure_gateway/bin/spacebridgeapp/rest/registration/saml_registration_handler.py", line 70, in post
    self_register = extract_parameter(request['query'], SELF_REGISTER_LABEL, QUERY_LABEL)
  File "/opt/splunk/etc/apps/splunk_secure_gateway/bin/spacebridgeapp/rest/util/helper.py", line 15, in extract_parameter
    raise Errors.SpacebridgeRestError('Error: Request requires %s parameter "%s"' % (source_name, key), 400)
spacebridgeapp.rest.util.errors.SpacebridgeRestError: Error: Request requires query parameter "self_register"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Any ideas on how to solve this issue? or continue the troubleshooting?&lt;/P&gt;</description>
    <pubDate>Mon, 09 May 2022 16:23:18 GMT</pubDate>
    <dc:creator>joshiro</dc:creator>
    <dc:date>2022-05-09T16:23:18Z</dc:date>
    <item>
      <title>Splunk Secure Gateway connection error</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Secure-Gateway-connection-error/m-p/596995#M12484</link>
      <description>&lt;P&gt;We are having a connection issue on Splunk Enterprise 8.2.6 on prem with Splunk Secure Gateway 2.7.4, according to the firewall rules the connection port 443 outbound to the host prod.spacebridge.spl.mobi is allowed.&lt;BR /&gt;&lt;BR /&gt;We verified the connection using the troubleshooting guide in the documentation by running:&lt;/P&gt;&lt;PRE&gt;curl https://prod.spacebridge.spl.mobi/health_check&lt;/PRE&gt;&lt;P&gt;Also we tried the test for wss connection and we get the correct response:&lt;/P&gt;&lt;PRE&gt;curl -i -N -H "Connection: Upgrade" -H "Upgrade: websocket" -H "Host: echo.websocket.events" -H "Origin: https://echo.websocket.events" -H "Sec-WebSocket-Key: d3d3LnNwbHVuay5jb20=" -H "Sec-WebSocket-Version: 13" https://echo.websocket.events&lt;/PRE&gt;&lt;P&gt;&lt;BR /&gt;When we run the following rest command:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;| rest "services/ssg/test_websocket" request_type="{\"versionGetRequest\": {}}" request_mode=clientSingleRequest&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We get this output:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;auth_code_status = 200
completed_client_registration = 0
error = 'token_id'
server_registration_status = 400
splunk_server = server
wss_response = 0&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;The error traceback in _internal is:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;2022-05-09 11:22:58,148 ERROR [rest_base] [__init__] [exception] [4772] Spacebridge error
Traceback (most recent call last):
  File "/opt/splunk/etc/apps/splunk_secure_gateway/bin/spacebridgeapp/rest/util/helper.py", line 13, in extract_parameter
    result = obj[key]
KeyError: 'self_register'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/opt/splunk/etc/apps/splunk_secure_gateway/bin/spacebridgeapp/rest/base_endpoint.py", line 53, in handle
    res = self.handle_request(request)
  File "/opt/splunk/etc/apps/splunk_secure_gateway/bin/spacebridgeapp/rest/base_endpoint.py", line 86, in handle_request
    return self.post(request)
  File "/opt/splunk/etc/apps/splunk_secure_gateway/bin/spacebridgeapp/rest/registration/saml_registration_handler.py", line 70, in post
    self_register = extract_parameter(request['query'], SELF_REGISTER_LABEL, QUERY_LABEL)
  File "/opt/splunk/etc/apps/splunk_secure_gateway/bin/spacebridgeapp/rest/util/helper.py", line 15, in extract_parameter
    raise Errors.SpacebridgeRestError('Error: Request requires %s parameter "%s"' % (source_name, key), 400)
spacebridgeapp.rest.util.errors.SpacebridgeRestError: Error: Request requires query parameter "self_register"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;Any ideas on how to solve this issue? or continue the troubleshooting?&lt;/P&gt;</description>
      <pubDate>Mon, 09 May 2022 16:23:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Secure-Gateway-connection-error/m-p/596995#M12484</guid>
      <dc:creator>joshiro</dc:creator>
      <dc:date>2022-05-09T16:23:18Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Secure Gateway connection error</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Secure-Gateway-connection-error/m-p/690211#M19594</link>
      <description>&lt;P&gt;Hi Joshiro, how did you solve the issue? I'm facing the same problem to connect to Spacebridge to configure Splunk Edge Hub.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Marco&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2024 10:21:54 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Secure-Gateway-connection-error/m-p/690211#M19594</guid>
      <dc:creator>marcoscala</dc:creator>
      <dc:date>2024-06-10T10:21:54Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk Secure Gateway connection error</title>
      <link>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Secure-Gateway-connection-error/m-p/690255#M19596</link>
      <description>&lt;P&gt;Hi Marco, i dont really remember what was the problem nor the solution.&lt;BR /&gt;We are currently working with Splunk Edge Hub on Splunk 9.2.0.1 and we got no problems with the device registration.&lt;BR /&gt;&lt;BR /&gt;What i do remember about that time where we implemented the SSG for Mobile use, is that there was a problem with cert inspection on the firewall, it changed something on the cert itself ,and it was no longer recognized as a valid one for the SSG.&lt;BR /&gt;&lt;BR /&gt;Regards.&lt;/P&gt;</description>
      <pubDate>Mon, 10 Jun 2024 15:31:51 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Enterprise/Splunk-Secure-Gateway-connection-error/m-p/690255#M19596</guid>
      <dc:creator>joshiro</dc:creator>
      <dc:date>2024-06-10T15:31:51Z</dc:date>
    </item>
  </channel>
</rss>

