> concern is more to do with the fact that the Stored ID Data Connector
> generates the target ID using a different algorithm (Type 4 UUID?) to the
> one we currently use.
Only after revocation.
> SP's will expect the current value for old users.
> However our current target ID values should NOT get over-ridden? thus only
> new SP requests will generate the target ID based on the new algorithm? Is
> this correct? Hope this makes sense!
I've been through this loop for a couple of releases and as of the 2.1.5
release StoredID will produce the same as the old version first time round.
I would not recommend using StoredID before 2.1.5 (and you should test first