Password field for accounts created by social auth

Created on 26 June 2019, over 5 years ago
Updated 2 November 2023, about 1 year ago

I'm wondering what to do with the password fields for accounts that have been created with social_auth_google?

Can anyone recommend a strategy from their experience?

I current redirect users to the user/edit page at login so they can fill out the rest of their profile. Unfortunately, there Current Password, New Password, and Confirm Password fields make that page a bit redundant.

- How does the new account get its initial password? Would it be the same password as the account used in auth?
- Should those fields be hidden when the account was created by social_auth?
- Is there another way?

Thanks for your time.

💬 Support request
Status

Active

Component

User interface

Created by

🇨🇦Canada ydahi Waterloo, Canada

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • 🇮🇳India ankithashetty Karnataka, India

    +1 to this issue.
    We have a password_policy module + change_pwd_page module

    1. User Signed in via social login - Google for ex
    2. Due to the password_policy module & its config, password expiration gets enabled for the user after a few days. (based on the date set by admin)
    3. User tries to sign up again via social login. He is logged in but gets redirected to the change-password page (this page will have current pass and New pass fields shipped with the change_pwd_page module)
    4. User will be blocked as he will not be able to change the pass - because there was no 'current password' in the first place.
Production build 0.71.5 2024