DocuSign SSO issues on Dev environment.

[Cantor, Scott]

On 11/30/16, 6:18 PM, "users on behalf of IAM David Bantz" <users-bounces at shibboleth.net on behalf of dabantz at alaska.edu> wrote:

>    Our integration of DocuSign (only in demo instance to date) with Shibboleth IdP includes the re-set of email
> mentioned by Adrew Morgan, and also JIT provisioning at DocuSign: previously unseen uid (in the nameid in the
> subject!) creates a new account.  In the DocuSign admin console, users are identified by their email address (as
> provided by and possibly updated by the mail attribute in the IdP's SAML assertion), but there appears to be an
> underlying key based on the values you provide in the Subject nameid.

Then perhaps the only open question is what controls the NameID Format it's requesting.  If that's tuneable, that works quite well.

In either case, the OP's issue is self-evident. It's requesting persistent, no such format is supported, error. I'd just hate to see people forced to rush a persistent ID into production to handle an SP that I very much doubt really requires that.

-- Scott