Persistent NameID

[Tom Poage]

> On Feb 16, 2017, at 2:47 PM, Cantor, Scott <cantor.2 at osu.edu> wrote:
> 
...
>> Digging through the documentation on NameID’s it mentions using a
>> database to store Persistent NameIDs.  It looks like there is quite a bit of
>> things that can happen with these NameIDs.  I don’t want to create a hash or
>> do anything like that, since the information is already sitting in Active
>> Directory and is being returned then I don’t feel like a database is honestly
>> required here. If it is that is fine and I can easily get this all setup based on the
>> wiki.
> 
> Yes, which is why what you're talking about is not a persistent NameID.
> 
>> Do I need to setup a database server just to use Persistent NameID’s?
> 
> You don't need to set one up to use Persistent NameIDs, but you do not want to use them anyway.

I haven't been keeping a close eye on federation plans wrt their IdP Attribute Profiles (1). What is the recommended/expected replacement for SAML Persistent NameID? Something IdPO's generate themselves, such as eduPersonUniqueId?

Thanks.
Tom.

[1] https://wiki.edugain.org/IDP_Attribute_Profile:_recommended_attributes