authgear / authgear/authgear-server

Improve the re-authentication experience on portal

Open
#3,269 0 comments 0 reactions 0 assignees View on GitHub
pitch
Dominant language
Go
Stars
2k
Forks
125
Avg merge
2d 17h
Merged PRs (30d)
32

Description

**Problem**
Users who signed up with Google cannot perform re-authentication. They were blocked from performing sensitive operations, like revealing a secret.

**Appetite**
2 weeks.

**Solution**
After Workflow is shipped

- If the user has means to re-authenticate, require them to re-authenticate before performing sensitive operations.
- If the user has no means to re-authenticate, show a message to ask them to set up 2FA. After that, they can re-authenticate.

**Rabbit holes**
The user who set up 2FA for this reason has to perform 2FA when they sign in.

**No-goes**
Not applicable.

Contributor guide

Open the contributing guide

Research direction

Start by tracing the portal flow for sensitive operations and how users who signed up with Google currently reach re-authentication. Review the existing 2FA setup and sign-in paths before implementing the stated behavior: require re-authentication when available, or guide users without a method to set up 2FA, then verify both paths.

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
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.