Multiple providers, multiple accounts, multiple verified emails

[annaghi]

Hello,

I'm reaching out to discuss a feature that our team is keen to explore: the ability to handle multiple accounts and manage multiple verified emails for a single user.

Below, you'll find a small example that illustrates the structure we're considering for the user_key.

auth_user table

id
111111111
222222222

user_key table (something like this)

id	user_id	provider_id	provider_user_id	verified_email
github:7777:[email protected]	111111111	github	7777	[email protected]
github:7777:[email protected]	111111111	github	7777	[email protected]
github:8888:[email protected]	111111111	github	8888	[email protected]
gitlab:aaaa:[email protected]	111111111	gitlab	aaaa	[email protected]
gitlab:aaaa:[email protected]	111111111	gitlab	aaaa	[email protected]
google:1212:[email protected]	111111111	google	1212	[email protected]
github:9999:[email protected]	222222222	github	9999	[email protected]

If either the provider_id + provider_user_id OR the verified_email exists in the user_key table, then it is not a new user.

I'd like to understand if this feature aligns with the current roadmap. Is there any plan or intention to support such a structure in the near future?

EDIT: Fixed the column names.

[pilcrowonpaper]

Hi, sorry for the late response. As of right now, we are not planning to add custom key attributes. It looks like a database transaction is needed anyway so I'd recommend using database queries directly. One advice for the data structure is to store the emails in a separated table connected to the user table.

[annaghi]

Hi, no problem. Thanks for the advice: a separate table for emails sounds reasonable.