- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I'm trying to communicate with Splunk via the API and I'm getting HTTP 303 errors when I attempt to get the session key. Usernames and passwords have been purposely filled with "user" and "pass". Example is based off of the Splunk documentation.
curl -u user:pass -k https://ourserver.host.com:8070/services/auth/login -d"username=user&password=pass"
I get this back (cURL reports an HTTP status of 303 - See Other):
This resource can be found at <a href='https://ourserver.host.com:8000/en-US/services/auth/login'>https://ourserver.host.com:8070/en-US/services/auth/login</a>.
So I try this:
curl -u user:pass -k https://ourserver.host.com:8070/en-US/services/auth/login -d"username=user&password=pass"
...and I get a 404.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<!--
This is a static HTML string template to render errors. To edit this
template, see appserver/mrsparkle/lib/error.py.
-->
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:splunk="http://www.splunk.com/xhtml-extensions/1.0" xml:lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=utf-8" />
<title>The path '/en-US/services/auth/login' was not found. - Splunk</title>
<style>
[...]
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This solved my issue. Connecting to management port rather that the WEBUI port.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
It looks like you're hitting the SplunkWeb port, not the management port (aka Splunkd port).
If you dont know what your management port is, login as the admin user, and go to Manager > System Settings > General Settings.
the default value is 8089, but since your SplunkWeb port is 8070 instead of 8000, im guessing the other one was changed too.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
This solved my issue. Connecting to management port rather that the WEBUI port.
