DocuSign SSO issues on Dev environment.

[Dr_Natas]

This is AuthRequest that I get when using the url redirect to our testing
environment.

<samlp:AuthnRequest ID="_2ccf0ea0-0887-49f5-9a50-b27cd9e985c8"
                    Version="2.0"
                    IssueInstant="2016-12-01T00:25:12.177Z"
                   
Destination="https://209.129.116.15/idp/profile/SAML2/POST/SSO"
                    ForceAuthn="false"
                    IsPassive="false"
                   
ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
                   
AssertionConsumerServiceURL="https://account-d.docusign.com/organizations/37269197-2dd0-49da-8668-526cfe2e4c56/saml2/login"
                    xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol"
                    >
    <saml:Issuer
xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">https://account-d.docusign.com/organizations/37269197-2dd0-49da-8668-526cfe2e4c56/saml2</saml:Issuer>
    <samlp:NameIDPolicy
Format="urn:oasis:names:tc:SAML:2.0:nameid-format:persistent"
                        AllowCreate="true"
                        />
</samlp:AuthnRequest>


When I sign in using a test account keep getting the InvalidNameIDPolicy. A
official meeting with DocuSign will be this Friday 12:30 pm pacific time.
That InvalidNameIDPolicy still hunts me. 



            </ds:X509Data>
        </ds:KeyInfo>
    </ds:Signature>
    <saml2p:Status>
        <saml2p:StatusCode
Value="urn:oasis:names:tc:SAML:2.0:status:Requester">
            <saml2p:StatusCode
Value="urn:oasis:names:tc:SAML:2.0:status:InvalidNameIDPolicy" />
        </saml2p:StatusCode>
        <saml2p:StatusMessage>An error occurred.</saml2p:StatusMessage>
    </saml2p:Status>
</saml2p:Response>












-----
Thank you!
--
View this message in context: http://shibboleth.1660669.n2.nabble.com/DocuSign-SSO-issues-on-Dev-environment-edit-for-complete-sentences-tp7629901p7629944.html
Sent from the Shibboleth - Users mailing list archive at Nabble.com.