I recently started working on a new system that will take in old accounts, new accounts setup both with SSO and Email, so came up with this pattern. All usernames are generated and used more as ID's in the system.
SSO (Using my service Hey.Café aka why called HC)
HC-SB3NX4L1E2
Email
EM-UTP3VW08H1
Legacy Imported Accounts
LE-SK7TTDVRHE
This way they never overlap but they are safe to share to the user, used for stuff like a user sharing an item to another. Plus it really helps down the road to integrate with anything as they are tokens that can be used anywhere as a token.
I recently started working on a new system that will take in old accounts, new accounts setup both with SSO and Email, so came up with this pattern. All usernames are generated and used more as ID's in the system.
SSO (Using my service Hey.Café aka why called HC)
HC-SB3NX4L1E2
Email
EM-UTP3VW08H1
Legacy Imported Accounts
LE-SK7TTDVRHE
This way they never overlap but they are safe to share to the user, used for stuff like a user sharing an item to another. Plus it really helps down the road to integrate with anything as they are tokens that can be used anywhere as a token.