KB-1741 Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Jordan Horwat — Tue, 09 Oct 2018 08:59:09 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 10/9/2018 8:59:09 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

When configuring the Connected System Object to use OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

When using OAuth with a Connected System in Appian versions 17.4 to 18.2, Appian is using basic authentication but is also sending the 'client_id' and 'client_secret' credentials in the post data of the request against the token endpoint, as well as in the authorization header. This causes authentication against certain systems to fail with the above error.

This issue has been addressed in Appian 18.3.

Action

Upgrade to Appian version 18.3 or higher.

Affected Versions

This article applies to Appian 17.4 to Appian 18.2.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues

KB-1741 Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Jordan Horwat — Tue, 09 Oct 2018 09:23:41 GMT

Revision 11 posted to Appian Knowledge Base by Jordan Horwat on 10/9/2018 9:23:41 AM

Symptoms

When configuring the Connected System Object to use OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

This issue has been addressed in Appian 18.3.

Action

Upgrade to the Appian version 18.3 or higher.

Affected Versions

This article applies to Appian 17.4 to Appian 18.2.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues

KB-1741 Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Jordan Horwat — Tue, 09 Oct 2018 08:58:10 GMT

Revision 13 posted to Appian Knowledge Base by Jordan Horwat on 10/9/2018 8:58:10 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

When configuring the Connected System Object to use OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

This issue has been addressed in Appian 18.3.

Action

Upgrade to the Appian version 18.3 or higher.

Affected Versions

This article applies to Appian 17.4 to Appian 18.2.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues

KB-1741 Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Jordan Horwat — Tue, 09 Oct 2018 08:58:00 GMT

Revision 12 posted to Appian Knowledge Base by Jordan Horwat on 10/9/2018 8:58:00 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

When configuring the Connected System Object to use OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

This issue has been addressed in Appian 18.3.

Action

Upgrade to the Appian version 18.3 or higher.

Affected Versions

This article applies to Appian 17.4 to Appian 18.2.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues

KB-1741 Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Jordan Horwat — Tue, 09 Oct 2018 05:23:41 GMT

Revision 10 posted to Appian Knowledge Base by Jordan Horwat on 10/9/2018 5:23:41 AM

Symptoms

When configuring the Connected System Object to use OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

This issue has been addressed in Appian 18.3.

Action

Upgrade to the Appian version 18.3 or higher.

Affected Versions

This article applies to Appian 17.4 to Appian 18.2.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues

DRAFT KB-XXXX Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Tom Ryan — Thu, 04 Oct 2018 19:54:54 GMT

Revision 9 posted to Appian Knowledge Base by Tom Ryan on 10/4/2018 7:54:54 PM

Symptoms

When configuring the Connected System Object to use OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

This issue has been addressed in Appian 18.3.

Action

Upgrade to the Appian version 18.3 or higher.

Affected Versions

This article applies to Appian 17.4 to Appian 18.2.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues

DRAFT KB-XXXX Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Jordan Horwat — Thu, 04 Oct 2018 11:53:25 GMT

Revision 8 posted to Appian Knowledge Base by Jordan Horwat on 10/4/2018 11:53:25 AM

Symptoms

When configuring the Connected System Object to use OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

In the Appian OAuth 2.0 implementation, Appian is using basic authentication but is also sending the 'client_id' and 'client_secret' credentials in the post data of the request against the token endpoint, as well as in the authorization header. This causes authentication against certain systems to fail with the above error.

This issue has been addressed in the release of Appian 18.3.

Action

Upgrade to the latest version of Appian.

Affected Versions

This article applies to Appian 17.4 to Appian 18.2.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues

DRAFT KB-XXXX Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Jordan Horwat — Thu, 04 Oct 2018 11:15:40 GMT

Revision 7 posted to Appian Knowledge Base by Jordan Horwat on 10/4/2018 11:15:40 AM

Symptoms

When configuring the Connected System Object to use OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

This issue has been addressed in the release of Appian 18.3.

Action

Upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues

DRAFT KB-XXXX Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Jordan Horwat — Tue, 02 Oct 2018 21:25:09 GMT

Revision 1 posted to Appian Knowledge Base by Jordan Horwat on 10/2/2018 9:25:09 PM

Symptoms

When configuring the Connected System Object using OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

In the Appian OAuth 2.0 implementation, Appian is using basic authentication but also sending the client_id and client_secret credentials in post data of request against token endpoint, as well as in the authorization header. This causes authentication against certain systems to fail with the above error.

This issue has been addressed via AN-104714 in the release of Appian 18.3.

Action

Upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues

DRAFT KB-XXXX Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Jordan Horwat — Tue, 02 Oct 2018 17:33:20 GMT

Revision 6 posted to Appian Knowledge Base by Jordan Horwat on 10/2/2018 5:33:20 PM

Symptoms

When configuring the Connected System Object to use OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

In the Appian OAuth 2.0 implementation, Appian is using basic authentication but also sending the 'client_id' and 'client_secret' credentials in the post data of request against token endpoint, as well as in the authorization header. This causes authentication against certain systems to fail with the above error.

This issue has been addressed via AN-104714 in the release of Appian 18.3.

Action

Upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues

DRAFT KB-XXXX Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Jordan Horwat — Tue, 02 Oct 2018 17:32:48 GMT

Revision 5 posted to Appian Knowledge Base by Jordan Horwat on 10/2/2018 5:32:48 PM

Symptoms

When configuring the Connected System Object to use OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

This issue has been addressed via AN-104714 in the release of Appian 18.3.

Action

Upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues

DRAFT KB-XXXX Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Jordan Horwat — Tue, 02 Oct 2018 17:31:24 GMT

Revision 4 posted to Appian Knowledge Base by Jordan Horwat on 10/2/2018 5:31:24 PM

Symptoms

When configuring the Connected System Object to use OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

This issue has been addressed via AN-104714 in the release of Appian 18.3.

Action

Upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues

DRAFT KB-XXXX Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Jordan Horwat — Tue, 02 Oct 2018 17:29:56 GMT

Revision 3 posted to Appian Knowledge Base by Jordan Horwat on 10/2/2018 5:29:56 PM

Symptoms

When configuring the Connected System Object to use OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

In the Appian OAuth 2.0 implementation, Appian is using basic authentication but also sending the 'client_id' and 'client_secret' credentials in post data of request against token endpoint, as well as in the authorization header. This causes authentication against certain systems to fail with the above error.

This issue has been addressed via AN-104714 in the release of Appian 18.3.

Action

Upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues

DRAFT KB-XXXX Configuring the Connected System Object for OAuth 2.0 integration fails with "The client MUST NOT use more than one authentication method in each request." pink box error

Jordan Horwat — Tue, 02 Oct 2018 17:26:25 GMT

Revision 2 posted to Appian Knowledge Base by Jordan Horwat on 10/2/2018 5:26:25 PM

Symptoms

When configuring the Connected System Object using OAuth 2.0, pressing Authorize returns the following pink box error:

Cause

This issue has been addressed via AN-104714 in the release of Appian 18.3.

Action

Upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2018

Tags: known issues, integration, authentication, fixed issues