Skip to main content
arrow-left Back to Docusign.com
C
Docusign Employee
Community UserDocusign Employee
Legacy User
October 7, 2020
Solved

What is the solution for the "The response assertion is missing a required attribute" error faced by our user when she logs in to her Docusign account.

  • October 7, 2020
  • 13 replies
  • 4636 views

What is the solution for the "The response assertion is missing a required attribute" error faced by our user when she logs in to her Docusign account. 

Best answer by Community Expert

We were able to resolve the problem we were having. Not sure if our resolution is specific to us or will help everyone. We had to do a few things.

First (in azure) fill out the user attributes & claims

  • givenname - user.givenname
  • surname - user.surname
  • emailaddress - user.mail
  • name - user.userprincipalname
  • Unique User Identifier - user.userprincipalname

Next make sure that all users have a first name, last name, and email in the system.

13 replies

Show previous replies
C
Docusign Employee
Community MemberDocusign Employee
Legacy User
May 17, 2021

Mate you are a legend. I honestly cant say thanks enough! We are moving to DocuSign over to Duo hosted SSO and this one was killing me. DocuSign documentation is shocking! However what you have provided as got me up and running. Again big thanks mate.

C
Docusign Employee
Community MemberDocusign Employee
Legacy User
May 17, 2021

- Cheers! - glad I could help.

B
Newcomer
bankcfcuNewcomer
Newcomer
March 13, 2025

Here is the solution that worked for me to resolve the error, “The response assertion is missing a required attribute.”

Microsoft Entra had a default Name identifier format set to Email address. However, the saml2 response, once decoded, showed that DocuSign expected the format to be Persistent. After changing the Name identifier format to Peristent, the SSO worked.

<NameID Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent">

Code of ConductAccessibility statement

Docusign Community

Code of Conduct