[GH-ISSUE #690] Bug: The 'Update password' should not be visible or accessible for OAuth signup/login. #199

Closed
opened 2026-02-26 18:45:50 +03:00 by kerem · 3 comments
Owner

Originally created by @anikdhabal on GitHub (Nov 27, 2023).
Original GitHub issue: https://github.com/documenso/documenso/issues/690

Originally assigned to: @anikdhabal on GitHub.

Issue Description

Currently, even if someone is signed up or logged in through Google, the 'update password' field is still visible to them.

Expected Behavior

The 'update password' field should only be visible to users who have signed up using email and password. For OAuth users, display a message in the update password section indicating that password updates are not applicable or directing them to the respective OAuth provider for security management.

Screenshot 2023-11-27 235730

Current Behavior

No response

Screenshots (optional)

No response

Operating System [e.g., Windows 10]

No response

Browser [e.g., Chrome, Firefox]

No response

Version [e.g., 2.0.1]

No response

Please check the boxes that apply to this issue report.

  • I have searched the existing issues to make sure this is not a duplicate.
  • I have provided steps to reproduce the issue.
  • I have included relevant environment information.
  • I have included any relevant screenshots.
  • I understand that this is a voluntary contribution and that there is no guarantee of resolution.
  • I want to work on creating a PR for this issue if approved
Originally created by @anikdhabal on GitHub (Nov 27, 2023). Original GitHub issue: https://github.com/documenso/documenso/issues/690 Originally assigned to: @anikdhabal on GitHub. ### Issue Description Currently, even if someone is signed up or logged in through Google, the 'update password' field is still visible to them. ### Expected Behavior The 'update password' field should only be visible to users who have signed up using email and password. For OAuth users, display a message in the update password section indicating that password updates are not applicable or directing them to the respective OAuth provider for security management. ![Screenshot 2023-11-27 235730](https://github.com/documenso/documenso/assets/81948346/4c1d3322-72aa-4185-8e42-c1b5238371bd) ### Current Behavior _No response_ ### Screenshots (optional) _No response_ ### Operating System [e.g., Windows 10] _No response_ ### Browser [e.g., Chrome, Firefox] _No response_ ### Version [e.g., 2.0.1] _No response_ ### Please check the boxes that apply to this issue report. - [ ] I have searched the existing issues to make sure this is not a duplicate. - [ ] I have provided steps to reproduce the issue. - [ ] I have included relevant environment information. - [ ] I have included any relevant screenshots. - [ ] I understand that this is a voluntary contribution and that there is no guarantee of resolution. - [ ] I want to work on creating a PR for this issue if approved
Author
Owner

@anikdhabal commented on GitHub (Nov 27, 2023):

I want to tackle this one.

<!-- gh-comment-id:1828388212 --> @anikdhabal commented on GitHub (Nov 27, 2023): I want to tackle this one.
Author
Owner

@catalinpit commented on GitHub (Nov 30, 2023):

I want to tackle this one.

Assigned it to you!

<!-- gh-comment-id:1833246476 --> @catalinpit commented on GitHub (Nov 30, 2023): > I want to tackle this one. Assigned it to you!
Author
Owner

@github-actions[bot] commented on GitHub (Dec 30, 2023):

This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected

<!-- gh-comment-id:1872478496 --> @github-actions[bot] commented on GitHub (Dec 30, 2023): This issue has not seen activity for a while. It will be closed in 30 days unless further activity is detected
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/documenso#199
No description provided.