KB-2200 Generic SAML error in app server logs - "Idp Entity Id not stored on session or request"

Devon Lee — Wed, 09 Aug 2023 13:56:24 GMT

Current Revision posted to Appian Knowledge Base by Devon Lee on 8/9/2023 1:56:24 PM

Symptom

The following is observed in the application server log for Appian sites with SAML authentication configured:

ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

Cause

A SAML user failed to log in to Appian. This is a generic error that can have a variety of causes, including but not limited to:

User using incorrect credentials
User not added to correct SAML group
Expired SP or IdP certificate in the Admin Console SAML configuration
The IdP preventing the user from authenticating
Server time mismatch between Appian and the IdP

Action

Check whether SAML users are having issues logging in to Appian. If users are not facing issues, then the error can be safely ignored as it means some users had failed login attempts but were ultimately able to log in. If SAML users are having issues logging in, please review KB-1450 for troubleshooting steps to take. If this does not resolve the issue, open a case with Appian Technical Support and include the following:

When the issue started occurring, and if any SAML configuration changes were made recently on the Appian or IdP side.
A timestamp (with time zone) of a failed login attempt and (if self-managed) the application server log containing this timestamp.
A screenshot of the frontend error.
The scope of impact (i.e. all SAML users or only a subset). Note: details of each login attempt are recorded in login-audit.csv. More information about this log can be found here.
A SAML trace for a failed login attempt.

Affected Versions

This article applies to all versions of Appian using SAML authentication.

Last Reviewed: October 2021

Tags: How To, SAML, integration, authentication

KB-2200 Generic SAML error in app server logs - "Idp Entity Id not stored on session or request"

Elly Meng — Fri, 29 Oct 2021 14:31:58 GMT

Revision 14 posted to Appian Knowledge Base by Elly Meng on 10/29/2021 2:31:58 PM

Symptom

The following is observed in the application server log for Appian sites with SAML authentication configured:

ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

Cause

A SAML user failed to log in to Appian. This is a generic error that can have a variety of causes, including but not limited to:

User using incorrect credentials
User not added to correct SAML group
Expired SP or IdP certificate in the Admin Console SAML configuration
The IdP preventing the user from authenticating
Server time mismatch between Appian and the IdP

Action

When the issue started occurring, and if any SAML configuration changes were made recently on the Appian or IdP side.
A timestamp (with time zone) of a failed login attempt and (if self-managed) the application server log containing this timestamp.
A screenshot of the frontend error.
The scope of impact (i.e. all SAML users or only a subset). Note: details of each login attempt are recorded in login-audit.csv. More information about this log can be found here.
A SAML trace for a failed login attempt.

Affected Versions

This article applies to all versions of Appian using SAML authentication.

Last Reviewed: October 2021

Tags: How To, SAML, integration, authentication

DRAFT SP-6735 Generic SAML error in logs - "Idp Entity Id not stored on session or request"

Elly Meng — Thu, 28 Oct 2021 18:05:33 GMT

Revision 13 posted to Appian Knowledge Base by Elly Meng on 10/28/2021 6:05:33 PM

Symptom

The following is observed in the application server log for Appian sites with SAML authentication configured:

ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

Cause

A SAML user failed to log in to Appian. This is a generic error that can have a variety of causes, including but not limited to:

User using incorrect credentials
User not added to correct SAML group
Expired SP or IdP certificate in the Admin Console SAML configuration
The IdP preventing the user from authenticating
Server time mismatch between Appian and the IdP

Action

When the issue started occurring, and if any SAML configuration changes were made recently on the Appian or IdP side.
A timestamp (with time zone) of a failed login attempt and (if self-managed) the application server log containing this timestamp.
A screenshot of the frontend error.
The scope of impact (i.e. all SAML users or only a subset). Note: details of each login attempt are recorded in login-audit.csv. More information about this log can be found here.
A SAML trace for a failed login attempt.

Affected Versions

This article applies to all versions of Appian using SAML authentication.

Last Reviewed: October 2021

Tags: How To, SAML, integration, authentication

DRAFT SP-6735 Generic SAML error in logs - "Idp Entity Id not stored on session or request"

Elly Meng — Thu, 28 Oct 2021 18:05:11 GMT

Revision 12 posted to Appian Knowledge Base by Elly Meng on 10/28/2021 6:05:11 PM

Symptom

The following is observed in the application server log for Appian sites with SAML authentication configured:

ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

Cause

A SAML user failed to log in to Appian. This is a generic error that can have a variety of causes, including but not limited to:

User using incorrect credentials
User not added to correct SAML group
Expired SP or IdP certificate in the Admin Console SAML configuration
The IdP preventing the user from authenticating
Server time mismatch between Appian and the IdP

Action

When the issue started occurring, and if any SAML configuration changes were made recently on the Appian or IdP side.
A timestamp (with time zone) of a failed login attempt and (if self-managed) the application server log containing this timestamp.
A screenshot of the frontend error.
The scope of impact (i.e. all SAML users or only a subset). Note: details of each login attempt are recorded in login-audit.csv. More information about this log can be found here.
A SAML trace for a failed login attempt.

Affected Versions

This article applies to all versions of Appian using SAML authentication.

Last Reviewed: October 2021

Tags: How To, SAML, integration, authentication

DRAFT SP-6735 Generic SAML error in logs - "Idp Entity Id not stored on session or request"

kartik.khosa — Mon, 25 Oct 2021 19:03:53 GMT

Revision 11 posted to Appian Knowledge Base by kartik.khosa on 10/25/2021 7:03:53 PM

Symptom

The following is observed in the application server log for Appian sites with SAML authentication configured:

ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

Cause

A SAML user failed to log in to Appian. This is a generic error and can be due to a variety of reasons. Some of these reasons include but are not limited to:

Certification Expiration on Admin Console SAML configuration
Users not added in correct SAML groups
Significant mismatch between the clocks of the IdP and Appian

Action

Check whether SAML users whether or not they are having issues logging in to Appian. If users are not facing issues then the error can be safely ignored as it likely means that some users had failed login attempts but were ultimately able to log in. If users are facing an issue then please review KB-1450 for troubleshooting steps to take. If this does not resolve the issue, open a case with Appian Technical Support and include the following:

When the issue started occurring, and if any SAML configuration changes were made recently on the Appian or IdP side.
A timestamp (with time zone) of a failed login attempt and the application server log containing this timestamp.
A screenshot of the frontend error.
The scope of impact (e.g. all SAML users or only a subset).
- Note: details of each login attempt are recorded in login-audit.csv. More information about this log can be found here.
A SAML trace for a failed login attempt.

Affected Versions

This article applies to all versions of Appian using SAML authentication.

Last Reviewed: September 2021

Tags: How To, SAML, integration, authentication

DRAFT SP-6735 Generic SAML error in logs - "Idp Entity Id not stored on session or request"

kartik.khosa — Mon, 25 Oct 2021 18:57:39 GMT

Revision 10 posted to Appian Knowledge Base by kartik.khosa on 10/25/2021 6:57:39 PM

Symptom

The following is observed in the application server log for Appian sites with SAML authentication configured:

ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

Cause

A SAML user failed to log in to Appian. This is a generic error and can be due to a variety of reasons. Some of these reasons include but are not limited to:

Certification Expiration on Admin Console SAML configuration
Users not added in correct SAML groups
Significant mismatch between the clocks of the IdP and Appian

Action

Check whether SAML users are having issues logging in to Appian. If users are not facing issues then the error can be safely ignored as it likely means that some users had failed login attempts but were ultimately able to log in. If users are facing an issue then please review KB-1450 for troubleshooting steps to take. If this does not resolve the issue, open a case with Appian Technical Support and include the following:

When the issue started occurring, and if any SAML configuration changes were made recently on the Appian or IdP side.
A timestamp (with time zone) of a failed login attempt and the application server log containing this timestamp.
A screenshot of the frontend error.
The scope of impact (e.g. all SAML users or only a subset).
- Note: details of each login attempt are recorded in login-audit.csv. More information about this log can be found here.
A SAML trace for a failed login attempt.

Affected Versions

This article applies to all versions of Appian using SAML authentication.

Last Reviewed: September 2021

Tags: How To, SAML, integration, authentication

DRAFT SP-6735 Generic SAML error in logs - "Idp Entity Id not stored on session or request"

Elly Meng — Mon, 13 Sep 2021 22:57:27 GMT

Revision 9 posted to Appian Knowledge Base by Elly Meng on 9/13/2021 10:57:27 PM

Symptom

The following is observed in the application server log for Appian sites with SAML authentication configured:

ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

Cause

A SAML user failed to log in to Appian. This can be due to a variety of reasons, including incorrect credentials or an issue with the SAML configuration.

Action

Check whether SAML users are having issues logging in to Appian despite using correct credentials. If not, the error can be safely ignored as it likely means that some users had failed login attempts but were ultimately able to log in. If so, please review KB-1450 for troubleshooting steps to take. If this does not resolve the issue, open a case with Appian Technical Support and include the following:

When the issue started occurring, and if any SAML configuration changes were made recently on the Appian or IdP side.
A timestamp (with time zone) of a failed login attempt and the application server log containing this timestamp.
A screenshot of the frontend error.
The scope of impact (e.g. all SAML users or only a subset).
- Note: details of each login attempt are recorded in login-audit.csv. More information about this log can be found here.
A SAML trace for a failed login attempt.

Affected Versions

This article applies to all versions of Appian using SAML authentication.

Last Reviewed: September 2021

Tags: How To, SAML, integration, authentication

DRAFT SP-6735 How to Report Generic SAML Errors in tomcat-stdOut.log file

Elly Meng — Mon, 13 Sep 2021 22:51:43 GMT

Revision 8 posted to Appian Knowledge Base by Elly Meng on 9/13/2021 10:51:43 PM

Symptom

The following is observed in the application server log for Appian sites with SAML authentication configured:

ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

Cause

A SAML user failed to log in to Appian. This can be due to a variety of reasons, including incorrect credentials or an issue with the SAML configuration.

Action

When the issue started occurring, and if any SAML configuration changes were made recently on the Appian or IdP side.
A timestamp (with time zone) of a failed login attempt and the application server log containing this timestamp.
A screenshot of the frontend error.
The scope of impact (e.g. all SAML users or only a subset).
- Note: details of each login attempt are recorded in login-audit.csv. More information about this log can be found here.
A SAML trace for a failed login attempt.

Affected Versions

This article applies to all versions of Appian using SAML authentication.

Last Reviewed: September 2021

Tags: How To, SAML, integration, authentication

DRAFT SP-6735 How to Report Generic SAML Errors in tomcat-stdOut.log file

Elly Meng — Mon, 13 Sep 2021 22:49:51 GMT

Revision 7 posted to Appian Knowledge Base by Elly Meng on 9/13/2021 10:49:51 PM

Symptom

The following is observed in the application server log for Appian sites with SAML authentication configured:

[ajp-nio-0.0.0.0-8009-exec-3] ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

Cause

A SAML user failed to log in to Appian. This can be due to a variety of reasons, including incorrect credentials or an issue with the SAML configuration.

Action

When the issue started occurring, and if any SAML configuration changes were made recently on the Appian or IdP side.
A timestamp (with time zone) of a failed login attempt and the application server log containing this timestamp.
A screenshot of the frontend error.
The scope of impact (e.g. all SAML users or only a subset).
- Note: details of each login attempt are recorded in login-audit.csv. More information about this log can be found here.
A SAML trace for a failed login attempt.

Affected Versions

This article applies to all versions of Appian using SAML authentication.

Last Reviewed: September 2021

Tags: How To, SAML, integration, authentication

DRAFT SP-6735 How to Report Generic SAML Errors in tomcat-stdOut.log file

Elly Meng — Mon, 13 Sep 2021 22:43:01 GMT

Revision 6 posted to Appian Knowledge Base by Elly Meng on 9/13/2021 10:43:01 PM

Symptom

The following is observed in the application server log for Appian sites with SAML authentication configured:

[ajp-nio-0.0.0.0-8009-exec-3] ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

Cause

A SAML user failed to log in to Appian, which can be due to a variety of reasons such as incorrect credentials or an issue with the SAML configuration.

Action

When the issue first started occurring, and if any SAML configuration changes were made recently on the Appian or IdP side.
A timestamp (with time zone) of a failed login attempt and the application server log containing this timestamp.
A screenshot of the frontend error.
The scope of impact (e.g. all SAML users or only a subset).
- Note: details of each login attempt are recorded in login-audit.csv. More information about this log can be found here.
A SAML trace for a failed login attempt.

Affected Versions

This article applies to all versions of Appian using SAML authentication.

Last Reviewed: September 2021

Tags: How To, SAML, integration, authentication

DRAFT SP-6735 How to Report Generic SAML Errors in tomcat-stdOut.log file

kartik.khosa — Fri, 27 Aug 2021 21:27:15 GMT

Revision 5 posted to Appian Knowledge Base by kartik.khosa on 8/27/2021 9:27:15 PM

Symptom

When logging in to Appian, via a SAML authentication system, the following error can be printed in the application server log:

[ajp-nio-0.0.0.0-8009-exec-3] ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

Cause

This error indicates that a SAML user failed to authenticate. There are numerous causes that can print an error like that. Some of the issues can be related to the SAML setup or it may just be an incorrect credential attempt from an user.

Action

Check with front-end users to confirm if any are having issues logging into Appian. If SAML users do not complain about logging in, then the error most likely means some users failed to login temporarily, but were ultimately able to login. If users are not able to login after multiple login attempts, create a support ticket with the following information:

Tomcat-stdOut.log with the error and timestamp
Attach a screenshot of what users are seeing in the front end
Mention which users are being affected
1. Is it just some or all userss in the SAML group?
2. login-audit.csv file will have more details about the which users are unable to login in
Capture a SAML trace for the users who are facing issues logging in

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2021

Tags: How To, SAML

DRAFT SP-6735 How to Report Generic SAML Errors in tomcat-stdOut.log file

kartik.khosa — Fri, 27 Aug 2021 21:16:32 GMT

Revision 4 posted to Appian Knowledge Base by kartik.khosa on 8/27/2021 9:16:32 PM

Symptom

When logging in to Appian, via a SAML authentication system, the following error can be printed in the application server log:

[ajp-nio-0.0.0.0-8009-exec-3] ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

Cause

Action

If your users are complaining about continually not being able to login, you should create a support ticket with the following information:

Tomcat-stdOut.log with the error and timestamp
Attach a screenshot of what users are seeing in the front end
Mention which users are being affected
1. Is it just some or all userss in the SAML group?
2. login-audit.csv file will have more details about the which users are unable to login in
Capture a SAML trace for the users who are facing issues logging in

However, if your users do not complain about any login issues then the error most likely means that sometimes the users are typing incorrect credentials a few times before getting their credentials correct.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2021

Tags: How To, SAML

DRAFT SP-6735 How to Report Generic SAML Errors in tomcat-stdOut.log file

kartik.khosa — Fri, 27 Aug 2021 20:56:11 GMT

Revision 3 posted to Appian Knowledge Base by kartik.khosa on 8/27/2021 8:56:11 PM

Purpose

This KB highlights how to report a generic SAML error message to Appian Support. One example of the generic SAML error is shown in the application server log as follows:

[ajp-nio-0.0.0.0-8009-exec-3] ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

There are numerous causes that can print an error like that. Some of the issues can be related to the SAML setup or it may just be an incorrect credential attempt from an user.

Instructions

Report this issue to Appian Support with the following information:

Tomcat-stdOut.log with the error and timestamp
Attach a screenshot of what users are seeing in the front end
Mention which users are being affected
1. Is it just some or all userss in the SAML group?
2. login-audit.csv file will have more details about the which users are unable to login in
Capture a SAML trace for the users who are facing issues logging in

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2021

Tags: How To, SAML

DRAFT SP-6735 How to Report Generic SAML Errors in tomcat-stdOut.log file

kartik.khosa — Fri, 27 Aug 2021 20:53:32 GMT

Revision 2 posted to Appian Knowledge Base by kartik.khosa on 8/27/2021 8:53:32 PM

Purpose

This KB highlights how to report a generic SAML error message to Appian Support. One example of the generic SAML error is shown in the application server log as follows:

[ajp-nio-0.0.0.0-8009-exec-3] ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

There are numerous causes that can print an error like that. Some of the issues can be related to the SAML setup or it may just be an incorrect credential attempt from an user.

Instructions

Report this issue to Appian Support with the following information:

Tomcat-stdOut.log with the error and timestamp
Attach a screenshot of what users are seeing in the front end
Mention which users are being affected
1. Is it just some or all in the SAML group?
2. login-audit.csv file will have more details about the which users are unable to login in
Capture a SAML trace for the users who are facing issues with SAML

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2021

Tags: How To, SAML

DRAFT SP-6735 How to Report Generic SAML Errors in tomcat-stdOut.log file

kartik.khosa — Fri, 27 Aug 2021 20:52:52 GMT

Revision 1 posted to Appian Knowledge Base by kartik.khosa on 8/27/2021 8:52:52 PM

Purpose

This KB highlights how to report a generic SAML error message to Appian Support. One example of the generic SAML error is shown in the application server log as follows:

[ajp-nio-0.0.0.0-8009-exec-3] ERROR com.appiancorp.security.auth.saml.redirecter.SamlAuthProviderQueryStringGenerator - Could not find IdP entity Id: Idp Entity Id not stored on session or request

There are numerous causes that can present an error like that. Some of the issues can be related to the SAML setup or it may just be an incorrect credential attempt from an user.

Instructions

Report this issue to Appian Support with the following information:

Tomcat-stdOut.log with the error and timestamp
Attach a screenshot of what users are seeing in the front end
Mention which users are being affected
1. Is it just some or all in the SAML group?
2. login-audit.csv file will have more details about the which users are unable to login in
Capture a SAML trace for the users who are facing issues with SAML

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2021

Tags: How To, SAML