Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

500 error on /auth/login route #4162

Closed
zackkrida opened this issue Jan 23, 2025 · 2 comments · Fixed by #4166
Closed

500 error on /auth/login route #4162

zackkrida opened this issue Jan 23, 2025 · 2 comments · Fixed by #4166
Assignees
@pavish
Labels
affects: ux Related to user experience ready Ready for implementation restricted: maintainers Only maintainers can resolve this issue work: backend Related to Python, Django, and simple SQL
Milestone
v0.2.0 (beta rele...

Comments

@zackkrida
Copy link
Contributor

Description

A 500 error on the /auth/login route was identified in the following scenario:

When logging into Mathesar, if a user's password has been reset by an administrator, the user is prompted to create a new password. After doing so, the user must log in again, using the new password, to access Mathesar.

After setting the new password, the user is redirected to /auth/login which throws a 500 error.

After further testing, visiting this route (without a trailing slash) in incognito/private browsing also throws the 500 error.

Expected behavior

There should not be a 500 error or any differences between /auth/login/ and /auth/login.

To Reproduce

  • Visit a Mathesar instance's /auth/login route in a private/incognito browsing context

Environment

  • OS: (eg. macOS 10.14.6; Fedora 32)
  • Browser: (eg. Safari; Firefox)
  • Browser Version: (eg. 13; 73)
  • Other info:

Additional context
@zackkrida zackkrida added needs: triage This issue has not yet been reviewed by a maintainer affects: ux Related to user experience work: backend Related to Python, Django, and simple SQL needs: troubleshooting Issues that we can't reproduce or need to investigate further before picking a course of action and removed needs: triage This issue has not yet been reviewed by a maintainer labels Jan 23, 2025
@pavish pavish added ready Ready for implementation and removed needs: troubleshooting Issues that we can't reproduce or need to investigate further before picking a course of action labels Jan 23, 2025
@seancolsen seancolsen added this to the v0.2.0 (beta release) milestone Jan 23, 2025
@seancolsen seancolsen added regression restricted: maintainers Only maintainers can resolve this issue labels Jan 23, 2025
@pavish
Copy link
Member

pavish commented Jan 23, 2025

I'm removing the regression label since this bug existed in 0.1.7

@pavish pavish removed the regression label Jan 23, 2025
@pavish pavish mentioned this issue Jan 23, 2025
Merged
7 tasks
@pavish pavish linked a pull request Jan 24, 2025 that will close this issue
Fix 500 on /auth/login route after password change #4166
Merged
7 tasks
@mathemancer
Copy link
Contributor

Solved by #4166

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@pavish pavish

Labels
affects: ux Related to user experience ready Ready for implementation restricted: maintainers Only maintainers can resolve this issue work: backend Related to Python, Django, and simple SQL
Projects
None yet
Milestone
v0.2.0 (beta release)
Development

Successfully merging a pull request may close this issue.

Fix 500 on /auth/login route after password change mathesar-foundation/mathesar
4 participants
@seancolsen @zackkrida @mathemancer @pavish