Reused usernames and persistentIds

[Cantor, Scott]

On 10/22/14, 12:27 PM, "Ramon Pfeiffer" <ramon.pfeiffer at uni-tuebingen.de>
wrote:
>
>A solution that we came up with was to change the salt used while
>generating the persistentId at regular intervals. A similar approach
>would be to use a random salt each time a new persistentId is calculated.
>However, this would conflict with the SWITCH AAI's recommendation. In
>case of a random salt, it seems deep reprogramming of the uApprove
>plugin would be needed, which is not an option.

The uApprove plugin has nothing to do with persistent IDs, I'm pretty sure
you're confused about your issues there (or I don't understand the
interaction there). The IdP does that work generally.

>Did anybody experience similar problems? Any recommendations?

If you can't use the computed method, then you could deploy a database and
manage them that way, which is the recommended approach anyway. If you
can't do that, I guess I wouldn't support the attribute. My IdP doesn't,
because I can't. I'm not going to generate one I can't let people rely on.

-- Scott