Signed Request in an ADFS as SAML Connection Error

ConnectionsSingle Sign-On

Last Updated:

Overview

When trying to login using an Active Directory Federation Services (ADFS) as a SAML connection, login errors out with the following error:

No AssertionConsumerService is configured on the relying party trust '...' that matches the AssertionConsumerService ProtocolBinding 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect' specified by the request

Steps to Reproduce

  1. Create an ADFS as a SAML connection
  2. Enable the Sign Request toggle with protocol binding set to HTTP-Redirect
  3. Download the certificate
  4. Return to ADFS and load the downloaded certificate using the Signatures tab of the Relying Party properties dialog
  5. Try to login

 

Applies To

  • Active Directory Federation Services (ADFS)
  • SAML Connections

Cause

The signed request is being sent using REDIRECT and ADFS is unable to accept it. REDIRECT causes the request to be in the URL.

Solution

Change the Protocol Binding to HTTP-POST under Sign Request on the settings page of the connection in the Auth0 Dashboard.

Recommended content

No recommended content found...
Need more help? Visit the Community
Visit the Auth0 Community