About trutch

trutch · ‎02-10-2014

This just solved an issue with my Heavy Forwarder. The weird thing is that _internal is all ready whitelisted in system/default/outputs.conf forwardedindex.2.whitelist = (_audit|_internal) Thanks for following up and answering your own question!

trutch · ‎04-03-2012

I turned off https on one of my search heads and the proxy is functional again. Thanks!

trutch · ‎03-08-2012

Thanks for the response. The upgrade was from 4.2.3 to 4.3.1. I don't think the link you provided applies, as normal LDAP access works fine and I don't specify anything by IP. I only see the issues when I go through my proxy with SSO (as detailed here: http://docs.splunk.com/Documentation/Splunk/latest/Admin/Usesinglesign-onwithSplunk).

trutch · ‎03-07-2012

We currently have a proxy set up with an SSO user as deteiled here: http://docs.splunk.com/Documentation/Splunk/latest/Admin/Usesinglesign-onwithSplunk Some of our application teams use a proxy with SSO to display Splunk dashboards in an iframe on some of their sites. Prior to the 4.3 upgrade, the proxy worked as expected and all elements were displayed. Post upgrade, no search data is displayed but the static content displays properly. Accessing the dashboard without the proxy works fine. I've looked over the changelog for 4.3 and couldn't find any related changes or issues. The SSO debug page isn't showing errors and I've tried reverting the charts on one of my dashboards to flash to no avail. Can anyone help me out?

Posts	4
Solutions	0
Karma Given	14
Karma Received	1
Member Since	‎02-23-2011

Online Status	Offline
Date Last Visited	‎06-05-2020 02:02 AM

SSO Broken after Upgrade to 4.3.1

Re: Deployment monitor and intermediary forwarder

Re: SSO Broken after Upgrade to 4.3.1

Re: SSO Broken after Upgrade to 4.3.1

SSO Broken after Upgrade to 4.3.1