authgear / authgear/authgear-server

Allow adding a "reason" for re-auth flow

Open
#3,249 1 comment 0 reactions 0 assignees View on GitHub
cooldown/minor-feature pitch
Dominant language
Go
Stars
2k
Forks
125
Avg merge
2d 17h
Merged PRs (30d)
32

Description

**Problem**
Right now, when a certain action trigger a re-auth flow, users will be redirected immediately to the *Enter password* screen. Which is confusing for users.

For example, when you download the Admin API keys in Authgear Portal:

![SCR-20230724-mai](https://github.com/authgear/authgear-server/assets/387241/e6b59dfb-e008-4a89-96c9-260bbd0d7313)

You will be redirected to this page immediately:
![SCR-20230724-mb6](https://github.com/authgear/authgear-server/assets/387241/3e29ae2e-a38c-4282-9e4d-1cfd9109b4bd)

It is confusing, as users do not know why they have to type the password, it feel even like a phishing page if you're supicious.

**Appetite**
1 or 2 weeks

**Solution**
One idea is whenever a re-auth flow might be trigger, we shall have a "reason" string as a parameter, and show that reason at a prominent area in the Enter Password screen.

**Rabbit holes**
Details about the solution worth calling out to avoid problems

**No-goes**
Functionality or use cases we intentionally aren’t covering to fit the appetite

Contributor guide

Open the contributing guide

Research direction

Start by tracing the re-authentication flow from the action trigger to the Enter Password screen, then identify the parameter and UI paths involved. Done means callers can provide a reason and users see it prominently before entering their password, with the affected flow covered by tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
authentication, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.