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!

Routing Data to Different Splunk Indexes in the OpenTelemetry Collector

This blog post is part of an ongoing series on OpenTelemetry. The OpenTelemetry project is the second largest ...

Getting Started with AIOps: Event Correlation Basics and Alert Storm Detection in ...

Getting Started with AIOps:Event Correlation Basics and Alert Storm Detection in Splunk IT Service ...

Register to Attend BSides SPL 2022 - It's all Happening October 18!

Join like-minded individuals for technical sessions on everything Splunk!  This is a community-led and run ...