Shib 3.2.1
Paul Hethmon
paul.hethmon at clareity.com
Fri Jun 23 15:16:25 EDT 2017
unspecified is not a real name format, it means “I don’t care what format you send me”.
In my experience there are 2 valid formats to use: transient and persistent
If you need anything else, then the SAML2 formats don’t apply (or at least extremely rare do they).
In my use cases, I always send the user’s Login ID. I’ve actually sent it as “unspecified” before, but it makes no sense. Maybe it does when you first read the standard.
Paul
> On Jun 23, 2017, at 2:43 PM, Cheltenham, Chris <ccheltenham-ext at philasd.org> wrote:
>
> We have a vendor asking is we can use unspecified nameID format.
> Wasn’t that deprecated in SAML 2.0?
>
> I have read the SAML documentation 100 times and I still don’t know what the hell they are talking about in that nameID section.
>
>
> ===========================
>
> Thank You;
>
> Chris Cheltenham
> Technology Services
> The School District of Philadelphia
>
> Work # 215-400-5025
> Cell # 215-301-6571
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net <mailto:users-unsubscribe at shibboleth.net>
Paul Hethmon
Chief Technology Officer
Clareity <http://www.clareity.com/> | 865.250.3517
Follow Us: LinkedIn <https://www.linkedin.com/company/clareity> | Twitter <https://twitter.com/TeamClareity> | Facebook <https://www.facebook.com/Clareity/>
Our Broker Dashboards have been nominated for an Inman Innovator Award! Check it out HERE <https://www.inman.com/list/innovators-2017/>.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20170623/2585d020/attachment.html>
More information about the users
mailing list