Inquiry ( third-party login)
In the current implementation of third-party login, I have observed that:
-- When the email returned by the third-party provider matches the email of an existing local account, the external identity is bound to that account.
-- When the emails do not match, the system automatically creates a brand-new account for the external identity.
I would like to clarify:
-
Is this the expected default behavior?
-
In cases where the emails do not match, is it possible to let the user manually choose between “bind to an existing account” or “create a new account”?
Background
This logic may cause the same real-world user to be recognized as multiple accounts due to differences in email addresses, which introduces challenges for user experience and data management. Therefore, I would like to confirm the intended design principle of the current binding mechanism and whether there are extensible configurations or recommended practices.
