Skip to main content
ArcBlock Community

Unable to Bind Third-Party Login: "Your account already exists"

Thumbler
Developers
blocklet-serverbugknown

Bug Description: Users are unable to link their account with third-party login services (Google, Apple, or GitHub) through the Settings > Third Party Login menu. When attempting to click the Connect button, the following error message appears: "Your account already exists, so binding cannot be completed."

Steps to Reproduce:

  1. Log in to the ArcBlock platform.
  2. Navigate to Settings > Third Party Login.
  3. Select one of the third-party login services (Google, Apple, or GitHub).
  4. Click the Connect button.

Screenshot 2024-11-29 220516.png

Expected Result: The user's account successfully links to the selected third-party login service without any errors.

Actual Result: An error message appears in red: "Your account already exists, so binding cannot be completed." The process fails even though there is no indication that the user's account was already linked to the selected service.

Impact: Users cannot utilize third-party login services, potentially causing confusion and a poor user experience, particularly for those relying on such methods for easy account access.

2 replies

wangshijun22 months ago

Hi, this happens when you login in following steps:

  • you have logged into this site directly with your social account without setup your DID Wallet, say test@gmail.com, and get DID A
  • then you login directly with your DID Wallet, and get DID B
  • then try bind test@gmail.com to your DID Wallet, above error will throw

There is no way to merge A and B now, but you have control over them all.

Thumbler22 months ago

Thank you for the explanation provided. However, the described situation highlights potential design issues within the system that could significantly impact user experience. Here are a few key points of concern:

  1. Lack of Clarity in the Login Process:
  • The system does not provide adequate information to users that logging in with different methods (social account vs. DID Wallet) will create a new DID. This can lead to confusion, especially for users unfamiliar with the concept of a DID Wallet.
  1. No Mechanism to Resolve Account Conflicts:
  • The absence of a feature to merge or align accounts (DID A and DID B) leaves users stuck in a situation where they cannot manage their accounts effectively. This could reduce trust in the platform.
  1. Platform Responsibility to Prevent Conflicts:
  • As a user-centric system, the platform should prioritize validation and conflict prevention mechanisms. If the same email is used, the system should provide warnings, options, or clear solutions before creating a new identity.
Reply