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
  • 4637 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

C
Docusign Employee
Community MemberDocusign Employee
Legacy User
October 9, 2020

I don't have an answer but we are seeing the same issue.

C
Docusign Employee
Community MemberDocusign Employee
Legacy User
November 3, 2020

I have the same issue as well

C
Docusign Employee
Community MemberDocusign Employee
Legacy User
November 26, 2020

Anyone know? duo and docusgn certainly don't.

C
Docusign Employee
Community MemberDocusign Employee
Legacy User
November 28, 2020

Would like to know this as well...

C
Docusign Employee
Community MemberDocusign Employee
Legacy User
December 1, 2020

Duo (our 2FA) have been extremely helpful -spent hours with me on this - here is their reply -

"Was DocuSign support able to identify the missing attribute that is generating the error message during their ingestion of the saml response?

  If they can identify what attribute is missing or misconfigured, specifically, we can correct that in the generic service provider settings and send them the correct attribute, we just need to know what is wrong. Their system is ingesting the saml response and generating the error message. Only they can identify the cause."

docusign - "Its not us, it's them, but we can't tell why"

C
Docusign Employee
Community ExpertDocusign EmployeeAnswer
Docusign Employee
December 1, 2020

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.

    C
    Docusign Employee
    Community MemberDocusign Employee
    Legacy User
    December 2, 2020

    Cheers - One question Is the Azure(we don't use it) attribute listed first - Looks like I will have to create custom Attributes on the Duo side.

    C
    Docusign Employee
    Community MemberDocusign Employee
    Legacy User
    December 2, 2020

    Looks like the right side is the "source" (Azure?) data. here are a couple of screenshots:

    overviewdetaileditem

    C
    Docusign Employee
    Community MemberDocusign Employee
    Legacy User
    December 3, 2020

    Ok, so with no thanks to DocuSign support, some thanks to Duo support (at least they would go over things) and many thanks to Nick for pointing me in the correct direction.

    Here is the answer for Duo generic SAML

    Capture 

    Docusign, your documentation sucks .

    C
    Docusign Employee
    Community MemberDocusign Employee
    Legacy User
    December 11, 2020

    These posts helped guide me to the answer for us. Thanks!

    A user encountered this issue and within our AD, his EmailAddress field was null. Update this to the correct value and he could log in.

    Show more replies
    Code of ConductAccessibility statement

    Docusign Community

    Code of Conduct