topic Re: How do I know the login status in Dashboards & Visualizations

How do I know the login status

junwhuan — Mon, 02 Dec 2013 14:45:21 GMT

Hello all,

I'm currently using java sdk to login splunk. How do I know the login status? Is there any session expiration time? If the login status is expired, I then can re-login it. Otherwise I don't want to login Splunk each time I do the searches.

Re: How do I know the login status

somesoni2 — Mon, 02 Dec 2013 15:12:42 GMT

Could you try using service.getToken method. I believe if session is expired, it should return null (or throw exception). Haven't verified it.

Re: How do I know the login status

junwhuan — Mon, 02 Dec 2013 15:23:21 GMT

I didn't try it. But I will try it now. Do they have documentation for the token?

Re: How do I know the login status

somesoni2 — Mon, 02 Dec 2013 17:29:30 GMT

Nothing much on documentation, but by description of the method, worth a try (gut feeling it might work)

Re: How do I know the login status

dfoster_splunk — Mon, 02 Dec 2013 22:12:15 GMT

Sessions expire after a certain amount of time - 60 minutes by default.

The only way to determine whether the session is still valid is to make a request and see whether it succeeds.

The Service.getToken() method that was mentioned by others will give you the current session token that is being used but it won't tell you whether it is valid or not. The Service object doesn't actually know whether it is still valid until a new request is made. Even after a timeout occurs the existing token isn't changed (or blanked out) until Server.login() is called again.

Re: How do I know the login status

junwhuan — Mon, 02 Dec 2013 22:12:32 GMT

It doesn't work. The token will be fetched locally. Even I log out.

Re: How do I know the login status

junwhuan — Mon, 02 Dec 2013 22:15:13 GMT

Could you please give me an example of this?

The only way to determine whether the session is still valid is to make a request and see whether it succeeds.

Re: How do I know the login status

dfoster_splunk — Mon, 02 Dec 2013 22:28:41 GMT

If you need to make an explicit check, something like the following should work:

service.getServiceInfo().getServerName(); // throws SplunkException if session invalid

However note that the session may time out by the time you send the next request. Therefore such an explicit check cannot reliably tell you whether a subsequent request will succeed.

A more robust solution is to harden any code that talks to Splunk to handle session timeouts, relogin if necessary, and reperform the request.