The current system generates persistent ids from the default nameid (usually email), and SP and IdP entity ids (generally URLs). A user email, service provider url, or identity provider url might change over time. In the previous system, this would change the PersistendId, leading to possible account loss on the client side. By using a random uuid stored in the database, this risk is alleviated.
The current system generates persistent ids from the default nameid (usually email), and SP and IdP entity ids (generally URLs). A user email, service provider url, or identity provider url might change over time. In the previous system, this would change the PersistendId, leading to possible account loss on the client side. By using a random uuid stored in the database, this risk is alleviated.