DocuSign SSO issues on Dev environment.

[IAM David Bantz]

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.

David

On Wed, Nov 30, 2016 at 2:05 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:

> On 11/30/16, 6:00 PM, "users on behalf of Andrew Morgan" <
> users-bounces at shibboleth.net on behalf of morgan at orst.edu> wrote:
>
> >    However, I'm pretty sure in my testing that I was able to change the
> email
> >    address released and have it update in Docusign (for the same NameID
> >    value), so that's actually kinda nice.
>
> Hmm, ok, I'll shut up then. That direct conflicts with things I was
> certain they told me over the phone about the new integration requirements,
> so without a formal document to point to, I'll assume I misheard or they
> misspoke. They seemed adamant about nothing having changed yet re: the
> email dependency, but it sounds like they've taken some initial steps on it.
>
> It also sounds like they have at least three different ways of
> integrating, so we're all just answering blind here, which I'm just tired
> of spending time doing.
>
> -- Scott
>
>
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at shibboleth.net
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20161130/b64c26dd/attachment.html>