Splunk Dev

Splunk Add-on for Microsoft Office 365 - failed to parse URL for IPv6

stwong
Communicator

Hi all,

In Splunk Add-on for Microsoft Office 365 (4.2.1) on Splunk Enterprise 9, we got problem when configuring it on a Splunk instance with IPv6 enabled:

2022-12-29 16:04:38,155 level=ERROR pid=2704844 tid=MainThread logger=splunk_ta_o365.modinputs.management_activity pos=utils.py:wrapper:72 | datainput=b'Staff_Management_Activity_AzureAD' start_time=1672301078 | message="Data input was interrupted by an unhandled exception."
Traceback (most recent call last):
File "/opt/splunk/etc/apps/splunk_ta_o365/lib/requests/models.py", line 434, in prepare_url
scheme, auth, host, port, path, query, fragment = parse_url(url)
File "/opt/splunk/etc/apps/splunk_ta_o365/lib/urllib3/util/url.py", line 397, in parse_url
return six.raise_from(LocationParseError(source_url), None)
File "<string>", line 3, in raise_from
urllib3.exceptions.LocationParseError: Failed to parse: https://::1:8089/servicesNS/nobody/splunk_ta_o365/configs/conf-inputs/splunk_ta_o365_management_acti...

Seems the localhost resolves to ::1 instead of [::1].    There is no problem if the host doesn't have IPv6 enabled.

Would anyone please help?

Thanks and Regards

Labels (2)
0 Karma
Get Updates on the Splunk Community!

Building Reliable Asset and Identity Frameworks in Splunk ES

 Accurate asset and identity resolution is the backbone of security operations. Without it, alerts are ...

Cloud Monitoring Console - Unlocking Greater Visibility in SVC Usage Reporting

For Splunk Cloud customers, understanding and optimizing Splunk Virtual Compute (SVC) usage and resource ...

Automatic Discovery Part 3: Practical Use Cases

If you’ve enabled Automatic Discovery in your install of the Splunk Distribution of the OpenTelemetry ...