PersistentNameIDGenerationConfiguration: Type 4 UUID
Cantor, Scott
cantor.2 at osu.edu
Tue Jan 23 20:09:18 EST 2018
On 1/23/18, 7:58 PM, "users on behalf of Hugo Slavia" <users-bounces at shibboleth.net on behalf of hugoslavia101 at gmail.com> wrote:
> For Stored IDs -- the options are base64 or base32 (idp.persistentId.encoding).
No, that's used for the hashed/computed version. The hash is binary so the encoding is the transform back into ASCII. You MUST use base32 if you want safe values. Base64 values are case sensitive and applications have botched this and do not allow use of case sensitive IDs, that's not safe.
> What could be the options of generating Type 4 for the Stored ID?
Stored IDs are UUIDs. But if you configure the IdP to generate the first generation of IDs using the computed strategy then you may never end up seeing any. That’s a migration tool to move from hashes to stored values.
I still don't know what you're asking. Literally, I am totally lost, I don't know what your question is.
-- Scott
More information about the users
mailing list