Briefly, this error occurs when the Assertion Consumer Service (ACS) URL registered for a Service Provider in Elasticsearch does not match the authentication request’s ACS URL. This mismatch can cause authentication failures. To resolve this issue, you can either update the registered ACS URL in the Service Provider’s configuration to match the one in the authentication request, or ensure that the authentication request is using the correct ACS URL as registered in the Service Provider’s configuration. Also, check for any typographical errors in the URLs.
This guide will help you check for common problems that cause the log ” The registered ACS URL for this Service Provider is [{}] but the authentication ” to appear. To understand the issues related to this log, read the explanation below about the following Elasticsearch concepts: plugin.
Log Context
Log “The registered ACS URL for this Service Provider is [{}] but the authentication” class name is SamlAuthnRequestValidator.java. We extracted the following from Elasticsearch source code for those seeking an in-depth context :
"SAML authentication does not contain an AssertionConsumerService URL. It contains an Assertion Consumer Service Index " +
"but this IDP doesn't support multiple AssertionConsumerService URLs.";
throw new ElasticsearchSecurityException(message; RestStatus.BAD_REQUEST);
}
if (acs.equals(sp.getAssertionConsumerService().toString()) == false) {
throw new ElasticsearchSecurityException("The registered ACS URL for this Service Provider is [{}] but the authentication " +
"request contained [{}]"; RestStatus.BAD_REQUEST; sp.getAssertionConsumerService(); acs);
}
return acs;
}
