Bug: Two competing forgot-password flows (app + Keycloak) #152
Labels
No labels
domain:backend
domain:devops
domain:frontend
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/westside-landing#152
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Bug
Lineage
Discovered during spike #150 — parent login flow validation.
Repo
forgejo_admin/westside-landingWhat Broke
Two independent password reset paths exist: the app's custom
/forgot-passwordflow (generates token, sends branded email, resets via basketball-api) and Keycloak's built-in "Forgot Password?" link on the login form (sends Keycloak-styled email, resets directly). Parents see different emails and UX depending on which link they click.Repro Steps
/signin→ click "Forgot Password?" → app's custom flow/signin→ click "Sign In" → on Keycloak form click "Forgot Password?" → Keycloak's built-in flowExpected Behavior
One consistent password reset flow, not two competing ones.
Environment
Acceptance Criteria
Related
project-westside-basketballforgejo_admin/westside-landing #150