Docusign

[Andrew Morgan]

On Mon, 8 Aug 2016, IAM David Bantz wrote:

> DocuSign is a net+ service provider, and the I2 site lists 15 subscribing
> institutions (
> http://www.internet2.edu/products-services/cloud-services-applications/docusign/docusign-subscribers/
> ).
>
> I'm hoping one or more of those 15 is represented here, and would be
> willing to share working IdPconfiguration. (When I last looked, the only
> option I could find was a less-than-robust proxy or relay through a third
> party vendor. I'm hoping for a direct integration between our Shibboleth
> IdP and Docusign.)
>
> David Bantz
> UAlaska

David,

*This OSU* has setup our IDP with Docusign in their demo environment.

A few things to note:

1. They do not consume nor publish metadata in InCommon.  They have an 
instance-specific entityID.  I asked them to publish their metadata.  They 
said they're working on it.  You should bug them too.

2. They require a "urn:oasis:names:tc:SAML:2.0:nameid-format:persistent" 
NameID, and they mean it.  The identifier must be persistent because they 
don't allow renames.

3. Turn encryption off.  They don't support it.

4. If you select Signed Requests, they have a bug that will always do a 
POST, so make sure you put a POST endpoint in for the URL.

I think that's it.  If you run into trouble, I can share our working 
config.

 	Andy