<?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 Re: node.js login error: no session key available in Security</title>
    <link>https://community.splunk.com/t5/Security/node-js-login-error-no-session-key-available/m-p/30973#M1028</link>
    <description>&lt;P&gt;In that case, I would try setting version to "4.3.2" instead of "4.0"&lt;/P&gt;</description>
    <pubDate>Mon, 12 Aug 2013 17:06:27 GMT</pubDate>
    <dc:creator>smohamed_splunk</dc:creator>
    <dc:date>2013-08-12T17:06:27Z</dc:date>
    <item>
      <title>node.js login error: no session key available</title>
      <link>https://community.splunk.com/t5/Security/node-js-login-error-no-session-key-available/m-p/30970#M1025</link>
      <description>&lt;P&gt;I am getting error: No session key available. Below is the node.js code in app.js. I'm getting the error at service.login() and then log the error. Please help. &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;var splunkjs = require('splunk-sdk'), 
Class = splunkjs.Class,
utils = splunkjs.Utils,
Async = splunkjs.Async;

app.get('/splunk', function(request, response) {
  // Create a Service instance and log in 
var service = new splunkjs.Service({
  scheme:"https",
  host:"&amp;lt;internal splunk address host&amp;gt;",
  port:"8089",
  username:"dashboard",
  password:"1234",
  version:"4.0"
});

//var service = new splunkjs.Service({username: "admin", password: "changeme"});
service.login(function(err, success) {
    if (err || !success) {
        console.log('Error: ' + err);
    }

    console.log("Login was successful: " + success);
    service.jobs().fetch(function(err, jobs) {
        var jobList = jobs.list();
        for(var i = 0; i &amp;lt; jobList.length; i++) {
            console.log("Job " + i + ": " + jobList[i].sid);
        }
    });
});
});
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Fri, 09 Aug 2013 23:47:25 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/node-js-login-error-no-session-key-available/m-p/30970#M1025</guid>
      <dc:creator>hm_splunk</dc:creator>
      <dc:date>2013-08-09T23:47:25Z</dc:date>
    </item>
    <item>
      <title>Re: node.js login error: no session key available</title>
      <link>https://community.splunk.com/t5/Security/node-js-login-error-no-session-key-available/m-p/30971#M1026</link>
      <description>&lt;P&gt;I was able to reproduce your issue.&lt;BR /&gt;
Which version of Splunk are you using? Make sure that matches the value you set for version in the splunkjs.service constructor.&lt;/P&gt;

&lt;P&gt;Try setting version to "default" and see if that solves your issue.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2013 16:26:32 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/node-js-login-error-no-session-key-available/m-p/30971#M1026</guid>
      <dc:creator>smohamed_splunk</dc:creator>
      <dc:date>2013-08-12T16:26:32Z</dc:date>
    </item>
    <item>
      <title>Re: node.js login error: no session key available</title>
      <link>https://community.splunk.com/t5/Security/node-js-login-error-no-session-key-available/m-p/30972#M1027</link>
      <description>&lt;P&gt;The splunk version is: &lt;BR /&gt;
Copyright © 2005-2013 Splunk Inc. All rights reserved.&lt;BR /&gt;
version 4.3.2, build 123586 &lt;/P&gt;

&lt;P&gt;I tried the "default" version but that didn't work&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2013 17:04:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/node-js-login-error-no-session-key-available/m-p/30972#M1027</guid>
      <dc:creator>hm_splunk</dc:creator>
      <dc:date>2013-08-12T17:04:14Z</dc:date>
    </item>
    <item>
      <title>Re: node.js login error: no session key available</title>
      <link>https://community.splunk.com/t5/Security/node-js-login-error-no-session-key-available/m-p/30973#M1028</link>
      <description>&lt;P&gt;In that case, I would try setting version to "4.3.2" instead of "4.0"&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2013 17:06:27 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/node-js-login-error-no-session-key-available/m-p/30973#M1028</guid>
      <dc:creator>smohamed_splunk</dc:creator>
      <dc:date>2013-08-12T17:06:27Z</dc:date>
    </item>
    <item>
      <title>Re: node.js login error: no session key available</title>
      <link>https://community.splunk.com/t5/Security/node-js-login-error-no-session-key-available/m-p/30974#M1029</link>
      <description>&lt;P&gt;That gives me a "404 not found" response.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2013 17:14:18 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/node-js-login-error-no-session-key-available/m-p/30974#M1029</guid>
      <dc:creator>hm_splunk</dc:creator>
      <dc:date>2013-08-12T17:14:18Z</dc:date>
    </item>
    <item>
      <title>Re: node.js login error: no session key available</title>
      <link>https://community.splunk.com/t5/Security/node-js-login-error-no-session-key-available/m-p/30975#M1030</link>
      <description>&lt;P&gt;If you are using 4.3, then you need to install the xml2json app. If you set it to 4.3 and it gives you a 404, that is likely the issue.&lt;/P&gt;</description>
      <pubDate>Mon, 12 Aug 2013 18:29:14 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Security/node-js-login-error-no-session-key-available/m-p/30975#M1030</guid>
      <dc:creator>ineeman</dc:creator>
      <dc:date>2013-08-12T18:29:14Z</dc:date>
    </item>
  </channel>
</rss>

