-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
splunklib.binding.AuthenticationError: Autologin succeeded, but there was an auth error on next request. Something is very wrong #486
Comments
Started getting this same error in the multiple addons. Seems like something is changed in the splunklib that is affecting multiple addons. Some of addons are
The Full error msg:
|
@RahulGuleria as per the discussion on the issue #219 bearer token is the feasible solution. and as mentioned by @ncanumalla-splunk managing of the bearer token is currently not in scope of SDK. @mahirchavda could you please share the Splunk and SDK versions being used. Also from the traceback you shared the error message was updated in the recent versions of the SDK. so we would request you to use the latest SDK and also please share the reproduction steps. |
Closing the Issue as we haven't received any response. @RahulGuleria , @mahirchavda please reopen the Issue if you still facing the issue. |
Is this issue resolved as I am still getting this error with version splunk-sdk==1.6.18 ?
As suggested on this thread,
#219
I have tried adding basic=True but that seems to be slowing down the splunk queries.
Is this slowness due to the fact that for all the queries it is doing authentication using username/password (as we are using basic=True).
service = client.connect(host=host_name,
scheme="https",
port=splunk_conf["port"],
username,
password,
autologin=True,
verify=False)
I tried with latest version splunk-sdk==1.7.2 also and started getting the below error
Exception while performing Splunk search. retry Count: 0... Authentication Failed! If session token is used, it seems to have been expire
Wanted to know if there is any other fix for this issue ?
Thanks in advance!
The text was updated successfully, but these errors were encountered: