Knowledge Management

assertionconsumerservice URL is missing from samlrequest in SP-initiated SSO flow.


I am currently working with our Okta team to get SSO working with Splunk. However, we cannot get the assertionconsumerservice URL to send. We've tried adding the field manually in authentications.conf and the field still doesn't send.


Here's the authentication.conf with some things removed.

authSettings = saml
authType = SAML

admin =


entityId = splunk-
fqdn =
idpCertPath = idpCert.pem
idpSSOUrl = https://(removed)
issuerId =
redirectAfterLogoutToUrl =
redirectPort = 0
AssertionConsumerServiceURL =
replicateCertificates = true
signAuthnRequest = false
signatureAlgorithm = RSA-SHA1
signedAssertion = true
sloBinding = HTTPPost
sslKeysfile = /opt/splunk/etc/auth/server.pem
sslKeysfilePassword =
ssoBinding = HTTPPost

0 Karma

Path Finder

remove that AssertionConsumeServerURL

create an okta local group on okta and map it to your admin user, and put it on the config there

admin = OktaGroupCreatedinOkta

test iDP initated login to splunk? if that works then SP initiated login should work now as well.

0 Karma

Path Finder

post your authentication.conf on the search head

0 Karma
Get Updates on the Splunk Community!

.conf24 | Day 0

Hello Splunk Community! My name is Chris, and I'm based in Canberra, Australia's capital, and I travelled for ...

Enhance Security Visibility with Splunk Enterprise Security 7.1 through Threat ...

 (view in My Videos)Struggling with alert fatigue, lack of context, and prioritization around security ...

Troubleshooting the OpenTelemetry Collector

  In this tech talk, you’ll learn how to troubleshoot the OpenTelemetry collector - from checking the ...