DocuSign SSO issues on Dev environment.
Klingenstein, Nate
nklingenstein at calstate.edu
Wed Nov 30 18:49:32 EST 2016
> There are two; persistent SAML NameIDs, and the eduPersonUniqueID
> attribute, which is its own NameID Format if need be.
There are at least two.
> We do. Coherent verbage doesn't fix people's unwillingness to accept
> limitations. SPs aren't willing to adopt requirements because that just costs
> customers, and so the answer is "whatever".
Why wouldn't the question be whatever with a couple parameters if the answer can be whatever if it matches those?
I'm still off on an island by myself, but I still feel like we're agonizingly close to a rough understanding of a general solution. Everything in this implementation rhymes with what I assembled in my dogma years ago, and I wouldn't change anything in that functionally.
More information about the users
mailing list