Hello there. Posting just for reference. It seems there is some misconfguration issue between splunkbase and the Splunk default config. The default config says: # /opt/splunk/bin/splunk btool ser...
See more...
Hello there. Posting just for reference. It seems there is some misconfguration issue between splunkbase and the Splunk default config. The default config says: # /opt/splunk/bin/splunk btool server list applicationsManagement | grep updateHost updateHost = https://apps.splunk.com # /opt/splunk/bin/splunk btool server list applicationsManagement | grep Check sslAltNameToCheck = splunkbase.splunk.com, apps.splunk.com, cdn.apps.splunk.com sslCommonNameToCheck = apps.splunk.com, cdn.apps.splunk.com However, the servers respond with: # curl -v https://apps.splunk.com 2>&1 | grep subject: * subject: C=US; ST=California; L=San Francisco; O=Splunk Inc.; CN=splunkbase.splunk.com Whereas 8.2.5 (don't have any other 8.2 at hand to check) seems to work despite those settings, 9.0.3 enforces the settings strictly and says ERROR X509 [25665 TcpChannelThread] - X509 certificate (CN=splunkbase.splunk.com,O=Splunk Inc.,L=San Francisco,ST=California,C=US) common name (splunkbase.splunk.com) did not match any allowed names (apps.splunk.com,cdn.apps.splunk.com) Walkaround: Overwrite the setting in server.conf with [applicationsManagement] sslCommonNameToCheck = splunkbase.splunk.com,apps.splunk.com,cdn.apps.splunk.com