KB-2153 Users see "Unexpected token < in JSON at position 0" error

Elly Meng — Wed, 03 Nov 2021 15:01:47 GMT

Current Revision posted to Appian Knowledge Base by Elly Meng on 11/3/2021 3:01:47 PM

Symptoms

Users that authenticate with SAML see the following error when navigating around Appian or interacting with an interface:

The error may also appear if one or more of the following apply:

The session timeout in Appian and the session timeout in the Identify Provider have different values.
Users are inactive in Appian for a prolonged period of time.
Users log out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Cause

This often occurs when the Appian session has timed out, and the user interacts with a SAIL interface. This issue has been hotfixed via AN-87093 in Appian 20.4 and later.

Action

Upgrade to Appian 20.4 or later.

Affected Versions

This article applies to Appian 20.3 and earlier.

Last Reviewed: November 2021

Tags: known issues, SAML, authentication, fixed issues

KB-2153 Users see "Unexpected token < in JSON at position 0" error

Nicholas Van Dyke — Fri, 18 Sep 2020 16:15:06 GMT

Revision 18 posted to Appian Knowledge Base by Nicholas Van Dyke on 9/18/2020 4:15:06 PM

Symptoms

Users that authenticate with SAML see the following error when navigating around Appian or interacting with an interface:

The error may also appear if one or more of the following apply:

The session timeout in Appian and the session timeout in the Identify Provider have different values.
Users are inactive in Appian for a prolonged period of time.
Users log out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Cause

This often occurs when the Appian session has timed out, and the user interacts with a SAIL interface. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-87093.

Action

Refresh the browser page.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2020

Tags: known issues, SAML, authentication, open issues

KB-2153 Users see "Unexpected token < in JSON at position 0" error

Nicholas Van Dyke — Fri, 18 Sep 2020 16:15:06 GMT

Revision 19 posted to Appian Knowledge Base by Nicholas Van Dyke on 9/18/2020 4:15:06 PM

Symptoms

Users that authenticate with SAML see the following error when navigating around Appian or interacting with an interface:

The error may also appear if one or more of the following apply:

The session timeout in Appian and the session timeout in the Identify Provider have different values.
Users are inactive in Appian for a prolonged period of time.
Users log out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Cause

Action

Refresh the browser page.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2020

Tags: known issues, SAML, authentication, open issues

DRAFT KB-[SP-3014] Users see "Unexpected token < in JSON at position 0" error

Zach Puderbach — Fri, 04 Sep 2020 13:22:03 GMT

Revision 17 posted to Appian Knowledge Base by Zach Puderbach on 9/4/2020 1:22:03 PM

Symptoms

Users that authenticate with SAML see the following error when navigating around Appian or interacting with an interface:

The error may also appear if one or more of the following apply:

The session timeout in Appian and the session timeout in the Identify Provider have different values.
Users are inactive in Appian for a prolonged period of time.
Users log out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Cause

Action

Refresh the browser page.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2020

Tags: known issues, SAML, authentication, open issues

DRAFT KB-[SP-3014] Users see "Unexpected token < in JSON at position 0" error

Nicholas Van Dyke — Thu, 03 Sep 2020 15:17:48 GMT

Revision 16 posted to Appian Knowledge Base by Nicholas Van Dyke on 9/3/2020 3:17:48 PM

Symptoms

Users that authenticate with SAML see the following error when navigating around Appian or interacting with an interface:

The error may also appear if one or more of the following apply:

The session timeout in Appian and the session timeout in the Identify Provider have different values.
Users are inactive in Appian for a prolonged period of time.
Users log out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Cause

HTML code is being evaluated directly in SAIL. This often occurs when the Appian session has timed out, and the authentication process is triggering directly in SAIL code instead of in the browser. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-87093.

Action

Refresh the browser page.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2020

Tags: known issues, SAML, authentication, open issues

DRAFT KB-[SP-3014]"Unexpected token < in JSON at position 0" Error

Zach Puderbach — Wed, 02 Sep 2020 18:25:56 GMT

Revision 15 posted to Appian Knowledge Base by Zach Puderbach on 9/2/2020 6:25:56 PM

Symptoms

Users that authenticate with SAML see the following error when navigating around Appian or interacting with an interface:

The error may also appear if one or more of the following apply:

The session timeout in Appian and the session timeout in the Identify Provider have different values.
Users are inactive in Appian for a prolonged period.
Users log out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Cause

Workaround

Refresh the browser page.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2020

Tags: known issues, SAML, authentication, open issues

DRAFT KB-[SP-3014]"Unexpected token < in JSON at position 0" Error

Zach Puderbach — Wed, 02 Sep 2020 18:25:29 GMT

Revision 14 posted to Appian Knowledge Base by Zach Puderbach on 9/2/2020 6:25:29 PM

Symptoms

Users that authenticate with SAML see the following error when navigating around Appian or interacting with an interface:

The error may also appear if one or more of the following apply:

The session timeout in Appian and the session timeout in the Identify Provider have different values.
Users are inactive in Appian for a prolonged period.
Users log out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Cause

Workaround

Refreshing the browser page.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: September 2020

Tags: known issues, SAML, authentication, open issues

DRAFT KB-[SP-3014]"Unexpected token < in JSON at position 0" Error

Zach Puderbach — Wed, 02 Sep 2020 18:22:39 GMT

Revision 13 posted to Appian Knowledge Base by Zach Puderbach on 9/2/2020 6:22:39 PM

Symptoms

Users that authenticate with SAML see the following error when navigating around Appian or interacting with an interface:

The error may also appear if one or more of the following apply:

The session timeout in Appian and the session timeout in the Identify Provider have different values.
Users are inactive in Appian for a prolonged period.
Users log out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Cause

Workaround

Refreshing the page will resolve the error and redirect the user to the Login Page.
In some instances, setting the Identity Provider session timeout to match the Appian session timeout will reduce the occurrence of this issue.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2020

Tags: known issues, SAML, authentication, open issues

DRAFT KB-[SP-3014]"Unexpected token < in JSON at position 0" Error

Zach Puderbach — Wed, 26 Aug 2020 23:46:03 GMT

Revision 12 posted to Appian Knowledge Base by Zach Puderbach on 8/26/2020 11:46:03 PM

Symptoms

Users that authenticate with SAML or with Native Authentication on a SAML enabled environment see the following error when navigating around Appian or interacting with an interface:

The error may also appear if one or more of the following apply:

The session timeout in Appian and the session timeout in the Identify Provider have different values.
Users are inactive in Appian for a prolonged period.
Users log out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Cause

This issue has been hotfixed via AN-87093 in Appian versions X.X to X.X.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Workaround

Refreshing the page will resolve the error and redirect the user to the Login Page.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2020

Tags: known issues, SAML, authentication, fixed issues

DRAFT KB-[SP-3014]"Unexpected token < in JSON at position 0" Error

Zach Puderbach — Fri, 14 Aug 2020 15:01:15 GMT

Revision 11 posted to Appian Knowledge Base by Zach Puderbach on 8/14/2020 3:01:15 PM

Symptoms

Users that authenticate with SAML see the following error when navigating around Appian or interacting with an interface:

The error may also appear if one or more of the following apply:

The session timeout in Appian and the session timeout in the Identify Provider have different values.
Users are inactive in Appian for a prolonged period.
Users log out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Cause

Workaround

Refreshing the page will resolve the error and redirect the user to the Login Page.
In some instances, setting the Identity Provider session timeout to match the Appian session timeout will reduce the occurrence of this issue.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2020

Tags: known issues, SAML, authentication, open issues

DRAFT KB-[SP-3014]"Unexpected token < in JSON at position 0" Error

Zach Puderbach — Tue, 28 Jul 2020 21:38:31 GMT

Revision 10 posted to Appian Knowledge Base by Zach Puderbach on 7/28/2020 9:38:31 PM

Symptoms

Users that authenticate with SAML see the following error when navigating around Appian or interacting with an interface:

The error may also appear if one or more of the following apply:

The session timeout in Appian and the session timeout in the Identify Provider have different values.
Users are inactive in Appian for a prolonged period.
Users log out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Cause

Workaround

In some instances, setting the Identity Provider session timeout to match the Appian session timeout will reduce the occurrence of this issue.
Refreshing the page will resolve the error and redirect the user to the Login Page.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2020

Tags: known issues, SAML, authentication, open issues

DRAFT KB-[SP-3014]"Unexpected token < in JSON at position 0" Error

Zach Puderbach — Tue, 28 Jul 2020 21:32:03 GMT

Revision 9 posted to Appian Knowledge Base by Zach Puderbach on 7/28/2020 9:32:03 PM

Symptoms

Users that authenticate with SAML see the following error when navigating around Appian or interacting with an interface:

The error may also appear if one or more of the following apply:

The session timeout in Appian and the session timeout in the Identify Provider have different values.
Users are inactive in Appian for a prolonged period.
Users log out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Cause

The Appian session has timed out, and the authentication process is triggering directly in SAIL code instead of in the browser. This issue has been reported to the Appian Product Team. The reference number for this issue is AN-87093.

Workaround

In some instances, setting the Identity Provider session timeout to match the Appian session timeout will reduce the occurrence of this issue.

Refreshing the page will resolve the error and redirect the user to the Login Page.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: July 2020

Tags: known issues, SAML, authentication

DRAFT KB-[SP-3014]"Unexpected token < in JSON at position 0" Error

Zach Puderbach — Tue, 18 Feb 2020 14:38:05 GMT

Revision 8 posted to Appian Knowledge Base by Zach Puderbach on 2/18/2020 2:38:05 PM

Symptoms

Users who authenticate using SAML see the following error when navigating around Appian:

This error appears after the following scenarios:

Users are inactive in Appian for a prolonged period, and the session timeout in Appian and the IdP have different values.
A user logs out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Other symptoms:

Refreshing the page causes the error to disappear.
A network capture's response content will show HTML for a webpage, usually the Appian or IdP login page.

Cause

The Appian session has timed out, and Appian is pulling the Login Page as HTML, rather then redirecting users to it.

Action

Refreshing the page will resolve the error.
There is currently a product enhancement to track this behavior in AN-87093.
IdP timeout should be the same as Appian Timeout

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2019

Tags: SAML

DRAFT KB-XXXX "Unexpected token < in JSON at position 0" Error

Zach Puderbach — Fri, 27 Sep 2019 17:43:20 GMT

Revision 7 posted to Appian Knowledge Base by Zach Puderbach on 9/27/2019 5:43:20 PM

Symptoms

Users who authenticate using SAML see the following error when navigating around Appian:

This error appears after the following scenarios:

Users are inactive in Appian for a prolonged period, and the session timeout in Appian and the IdP have different values.
A user logs out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Other symptoms:

Refreshing the page causes the error to disappear.
A network capture's response content will show HTML for a webpage, usually the Appian or IdP login page.

Cause

The Appian session has timed out, and Appian is pulling the Login Page as HTML, rather then redirecting users to it.

Action

Refreshing the page will resolve the error.
There is currently a product enhancement to track this behavior in AN-87093.
IdP timeout should be the same as Appian Timeout

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2019

Tags: SAML

DRAFT KB-XXXX "Unexpected token < in JSON at position 0" Error

Zach Puderbach — Fri, 27 Sep 2019 17:19:40 GMT

Revision 6 posted to Appian Knowledge Base by Zach Puderbach on 9/27/2019 5:19:40 PM

Symptoms

Users who login using SAML occasionally see the following error when navigating around Appian:

This error appears in the following scenarios:

Users are inactive in Appian for a prolonged period, and the session timeout in Appian and the IdP have different values.
A user logs out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Other symptoms:

Refreshing the page causes the error to disappear.
A network capture's response content will show HTML for a webpage, usually the Appian or IdP login page.

Cause

The Appian session has timed out, and Appian is pulling the Login Page as HTML, rather then redirecting users to it.

Action

Refreshing the page will resolve the error.
There is currently a product enhancement to track this behavior in AN-87093.
IdP timeout should be the same as Appian Timeout

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2019

Tags: SAML

DRAFT KB-XXXX "Unexpected token < in JSON at position 0" Error

Zach Puderbach — Fri, 27 Sep 2019 15:31:37 GMT

Revision 5 posted to Appian Knowledge Base by Zach Puderbach on 9/27/2019 3:31:37 PM

Symptoms

Users who login using SAML occasionally see the following error when navigating around Appian:

This error appears in the following scenarios:

Users are inactive in Appian for a prolonged period, and the session timeout in Appian and the IdP have different values.
A user logs out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tab, they see this error.

Other symptoms:

Refreshing the page causes the error to disappear.
A network capture will also show the Appian Login page being returned as content.

Cause

The Appian session has timed out, and Appian is pulling the Login Page as HTML, rather then redirecting users to it.

Action

Refreshing the page will resolve the error.
There is currently a product enhancement to track this behavior in AN-87093.
IdP timeout should be the same as Appian Timeout

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2019

Tags: SAML

DRAFT KB-XXXX "Unexpected token < in JSON at position 0" Error

Zach Puderbach — Fri, 27 Sep 2019 15:12:24 GMT

Revision 4 posted to Appian Knowledge Base by Zach Puderbach on 9/27/2019 3:12:24 PM

Symptoms

Refreshing the page causes the error to disappear.

A network capture will also show the Appian Login page being returned as content.

After a period of inactivity, see this error.
A user logs out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tag, they see this error.

Cause

The Appian session has timed out, and Appian is pulling the Login Page as HTML, rather then redirecting users to it.

Action

Refreshing the page will resolve the error.
There is currently a product enhancement to track this behavior in AN-87093.
IdP timeout should be the same as Appian Timeout

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2019

Tags: SAML

DRAFT KB-XXXX "Unexpected token < in JSON at position 0" Error

Zach Puderbach — Fri, 27 Sep 2019 15:02:08 GMT

Revision 3 posted to Appian Knowledge Base by Zach Puderbach on 9/27/2019 3:02:08 PM

Symptoms

Refreshing the page causes the error to disappear.

A network capture will also show the Appian Login page being returned as content.

After a period of inactivity, see this error.
A user logs out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tag, they see this error.

Cause

The Appian session has timed out, and Appian is pulling the Login Page as HTML, rather then redirecting users to it.

Action

Refreshing the page will resolve the error.
Product enhacemment
IdP timeout should be the same as Appian Timeout

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2019

Tags: SAML

DRAFT KB-XXXX "Unexpected token < in JSON at position 0" Error

Zach Puderbach — Fri, 27 Sep 2019 14:58:44 GMT

Revision 2 posted to Appian Knowledge Base by Zach Puderbach on 9/27/2019 2:58:44 PM

Symptoms

Refreshing the page causes the error to disappear.

After a period of inactivity, see this error.
A user logs out of Appian in one tab while still having Appian open in a second tab. When navigating around the second tag, they see this error.

Cause

The Appian session has timed out, and Appian is pulling the Login Page as HTML, rather then redirecting users to it.

Action

Refreshing the page will resolve the error.
Product enhacemment
IdP timeout should be the same as Appian Timeout

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2019

Tags: SAML

DRAFT KB-XXXX "Unexpected token < in JSON at position 0" Error

Zach Puderbach — Fri, 30 Aug 2019 21:21:18 GMT

Revision 1 posted to Appian Knowledge Base by Zach Puderbach on 8/30/2019 9:21:18 PM

Symptoms

Users that authenticate with SAML occasionally see a redbox error.

Users logout on one tab, and when navigating in another open Appian tab see this error

Cause

The Appian session has timed out, and Appian is pulling the Login Page as JSON, rather then redirecting users to it.

Action

Product enhacemment

IdP timeout should be the same as Appian Timeout

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: August 2019

Tags: SAML