Troubleshooting Chat Customer SSO
Chat creation requests can be denied due to various conditions. In such cases, the customer is shown an error message along with an error code. The error code varies based on the cause of the issue and helps the administrators narrow down the root cause.
|
Error Code |
Cause |
|---|---|
|
400-101 |
‘Apply Customer Chat Single Sign On’ is enabled for the entry point, but SAML assertion is missing in the chat request. Make sure that you are passing the SAML assertion in the chat creation request. |
|
400-102 |
If there is an expiration date time set in the SAML assertion, the assertion has expired by the time it reaches the application. |
|
400-103 |
EntityId present in the SAML assertion does not match the EntityId configured in the ‘Chat Customer Single Sign On’ in the Administration Console. |
|
400-104 |
Public key certificate configured for SAML in ‘Chat Customer Single Sign On’ in the Administration Console has expired. |
|
400-105 |
SAML assertion could not be validated using the public key configured in ‘Chat Customer Single Sign On’ in the Administration Console. Either the public key is incorrect or the SAML assertion has been tampered with. |
|
400-106 |
An attribute configured in ‘loginParameters’ in eGainLiveConfig.js file has the property ‘secureAttribute’ set to ‘1’, but it is missing from SAML assertion. |
|
400-107 |
Field validation failed for one or more chat attributes transferred in SAML assertion. The validation is configured for chat attributes in the ‘loginParameters’ in the eGainLiveConfig.js file. |
|
400-108 |
Any other miscellaneous errors such as ‘malformed XML’. |