proxy configuration for the Workday add on?

[sedogar_ews]

I have http_proxy and https_proxy set in my splunk-launch.conf file, and my proxy is set to not require auth for the workday.com URL, but I'm getting 401 errors. Running a trace on the proxy seems to indicate that traffic is never getting to the proxy.

I see errors like this:

2018-04-20 14:16:25,010 ERROR pid=2573
tid=MainThread
file=base_modinput.py:log_error:307 |
Request failed with error code (401),
retries exhausted

I also see this in the ta_workday_workday.log:

2018-04-20 14:21:18,092 INFO pid=4986
tid=MainThread
file=connectionpool.py:_new_conn:758 |
Starting new HTTPS connection (1):
127.0.0.1

Does the 127.0.0.1 indicate that the connectionpool.py is trying to hit localhost instead of the proxy for retrieval?

[3thanlewis · Accepted solution]

Part of the Workday Add-on is generated using Splunk's add-on builder app, which includes a module that specifically removes http_proxy/https_proxy environment variables. What you are seeing is the client connecting directly to the Workday API and receiving an HTTP 401 error. Make sure your tenant allows access by OAuth2 clients (https://community.workday.com/AddOnForSplunk) and that the other settings are accurate. The localhost connections are from the Add-on connecting to the local kvstore on your Splunk instance, for managing timestamp checkpoint values.

We are implementing proxy settings right now, expected to be in the next release (currently 0.4.1).

[rahutt]

Is there any estimated date for the next release of the Workday Add-on available yet?

[rahutt]

I see that proxy settings have now been added - https://splunkbase.splunk.com/app/3783/ (version 0.5.0).

[sedogar_ews]

Any idea of when the next release will happen?