Error Messages Related to SAML Authentication

Article Number:020450

This section provides solutions for an error screen displayed when configuring SAML authentication.

SLASH_SA01

Messages
No user account for that NameID found.
Cause
Kintone has no user whose login name matches the NameID in the SAML response.
Solutions
  • Configure your IdP so that the NameID specifies an element to identify a user.
  • Ensure that the value associated with the NameID corresponds to the login name of a Kintone user.

SLASH_SA02

Messages
Corresponding AuthnRequest not found.
Cause
This occurs in the following cases:
  • Multiple SAML requests were issued in one session.
    Example:
    • A user tried to single sign-on from multiple tabs in one Web browser.
    • After a user single signed-on, the user clicked the "Back" button of the Web browser to display the endpoint URL of Kintone.
  • An IdP-initiated SSO process was tried.
Solutions
  • Ensure that users do not perform actions that generate multiple SAML requests in one session.
  • Configure your IdP so that it can use SP-initiated SSO.

SLASH_SA03

Messages
The SAML response is not found in the request parameter.
Cause
There is no SAML response in the request parameter that the IdP sent to Kintone.
Solution
Confirm that nothing prevents the SAML response from being sent.

SLASH_SA04

Code
Invalid SAML Response.
Cause
There is no SAML response in the request parameter that the IdP sent to Kintone.
Solutions
Check the settings related to failed validation results.
Also refer to the following section:
Checking the Validation Results for the SAML Response

SLASH_SA05

Code
Invalid HTTP method. Use POST as the HTTP method.
Cause
HTTP POST Binding is not being used to send the SAML response.
Solutions
  • Configure the IdP so that HTTP POST Binding is used to send the SAML response.
  • Verify that the HTTP method was not changed to anything other than POST in a process such as a proxy server.

SLASH_FA01

Code
Failed to process SAML response.
Cause
The SAML response cannot be processed due to an unexpected error.
Solution
Contact our support.
How to Contact Us