KB-2047 Attempting to access Tempo after an upgrade results in a 403 Forbidden error for all users

Parmida Borhani — Thu, 02 Jan 2020 06:18:31 GMT

Current Revision posted to Appian Knowledge Base by Parmida Borhani on 1/2/2020 6:18:31 AM

Symptoms

After upgrading to a newer version of Appian, users experience a 403 Forbidden error when attempting to access Tempo regardless of authentication method or "Tempo Users" group membership. Users are still able to access the Admin Console, Designer, and Sites.

Cause

The newer version of Appian contains an updated whitelist-urlrewrite.xml file. The old whitelist-urlrewrite.xml file may have been copied over from the previous version rather than merged with the latest version.

Action

Merge any customizations with the new default whitelist-urlrewrite.xml file in <APPIAN_HOME>\ear\suite.ear\web.war\WEB-INF\conf\security\uri (JBoss) or <APPIAN_HOME>\deployment\web.war\WEB-INF\conf\security\uri (Tomcat) and restart the application server. For more information on updating configuration files, refer to the documentation.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: January 2020

Tags: 403, Tempo, upgrade, infrastructure

DRAFT KB-XXXX Attempting to access Tempo after an upgrade results in a 403 Forbidden error for all users

Nicholas Van Dyke — Mon, 30 Dec 2019 21:58:07 GMT

Revision 2 posted to Appian Knowledge Base by Nicholas Van Dyke on 12/30/2019 9:58:07 PM

Symptoms

Cause

Action

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2019

Tags: 403, Tempo, upgrade, infrastructure

DRAFT KB-XXXX Tempo returns 403 Forbidden error for all users after upgrade

Nicholas Van Dyke — Fri, 06 Dec 2019 20:51:46 GMT

Revision 1 posted to Appian Knowledge Base by Nicholas Van Dyke on 12/6/2019 8:51:46 PM

Symptoms

After upgrading to a newer version of Appian, users may experience a 403 Forbidden error when attempting to access Tempo regardless of authentication or "Tempo Users" group membership. In this case, users are still able to access the Admin Console, Designer, and sites.

Cause

The newer version of Appian contains an updated whitelist-urlrewrite.xml file with important authorization information. The old whitelist-urlrewrite.xml file may have been copied over from the previous version rather than merged with the latest version.

Action

Deploy the latest whitelist-urlrewrite.xml file in <APPIAN_HOME>\ear\suite.ear\web.war\WEB-INF\conf\security\uri (JBoss) or <APPIAN_HOME>\deployment\web.war\WEB-INF\conf\security\uri (Tomcat) and restart the application server.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: December 2019

Tags: upgrade, infrastructure