# Notify user that he previously uses Social Login

**URL:** <https://community.auth0.com/t/notify-user-that-he-previously-uses-social-login/87316>\
**Category:** Get Help\
**Created:** [July 20, 2022, 10:30pm UTC](https://community.auth0.com/t/notify-user-that-he-previously-uses-social-login/87316 "2022-07-20T22:30:41Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![swifteam](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/swifteam/32/33281_2.png) [@swifteam](https://community.auth0.com/u/swifteam)\
**Post date:** [July 20, 2022, 10:30pm UTC](https://community.auth0.com/t/notify-user-that-he-previously-uses-social-login/87316/1 "2022-07-20T22:30:41Z")

</div>

When a user signs up with database (password auth), but the user has used the social login already, how can we tell the person that he could try with the Social login (eg. Google)?

We’ve followed [the guide](https://community.auth0.com/t/invalid-signup-error-returns-instead-of-user-exists-from-authentication-api/29451/4) to change the tenant settings to display a user exists error instead of a generic error.

**But how can we further optimize the error message to show “You are using Google Login, please try again”?**

![image](https://global.discourse-cdn.com/auth0/original/3X/2/8/28002d42d45a37eb9a7297fa81a6f9741d343ac0.png)

---

<div class="post-metadata">

**Author:** ![swifteam](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/swifteam/32/33281_2.png) [@swifteam](https://community.auth0.com/u/swifteam)\
**Post date:** [July 20, 2022, 11:50pm UTC](https://community.auth0.com/t/notify-user-that-he-previously-uses-social-login/87316/2 "2022-07-20T23:50:50Z")

</div>

We decided to go with this approach to save complex user flow

1. When a Google Auth user signs up
2. [Use management API to create an email-password account](https://auth0.com/docs/api/management/v2#!/Users/post_users) with the same email address
3. Use a randomly generated password to prevent security risk
4. Set “email\_verified”: true (because this email is Google-authenticated already)
5. Now link this Google user account with this newly generated email-password user together by [the management API](https://auth0.com/docs/manage-users/user-accounts/user-account-linking/suggested-account-linking-server-side-implementation#metadata-merge-example)

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [July 28, 2022, 12:42pm UTC](https://community.auth0.com/t/notify-user-that-he-previously-uses-social-login/87316/3 "2022-07-28T12:42:19Z")

</div>

Thanks for sharing that with the rest of community!

---

<div class="post-metadata">

**Author:** ![konrad.sopala](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/konrad.sopala/32/13516_2.png) [@konrad.sopala](https://community.auth0.com/u/konrad.sopala)\
**Post date:** [July 28, 2022, 12:42pm UTC](https://community.auth0.com/t/notify-user-that-he-previously-uses-social-login/87316/4 "2022-07-28T12:42:21Z")

</div>


