IdP3 Clustering...

[Cantor, Scott]

> In fact, ComputedID is henceforth depreciated for that reason we use
> PersistentID with StoredID connector which generate random identifiers and
> store them in db.

Computing them hasn't been deprecated in any real way for a very long time. It's the only practical way to do them, a database is not a practical approach for the vast majority of deployers.

> It's easy to put in place dynamic PersistentID but it has some limitations ; it is
> not to possible to find a user with his PersistentID, revoke or  modify the
> value of the PersistentID...

The former is possible with audit logging. The latter isn't possible, but if it ever came up, building a mechanism based on a sparse override file to force changes to the hashes would be well within any mildly competent Java developer's capability.

-- Scott