goauthentik / goauthentik/authentik

Built-in email verification process for OAuth scope mapping

Open
#23,390 0 comments 4 reactions 0 assignees View on GitHub
enhancement/confirmed
Dominant language
Python
Stars
25.6k
Forks
2k
Avg merge
1d 2h
Merged PRs (30d)
651

Description

Since 2025.10 we no longer send the email_verified value via scope mappings: https://docs.goauthentik.io/releases/2025.10/#default-oauth-scope-mappings

This means that users now need to create a custom scope mapping for applications that require verified emails: https://docs.goauthentik.io/add-secure-apps/providers/oauth2/#email-scope-verification

It would be good if we could include an email verification system out of the box so that users don't need to configure this themselves.

Linked to: https://github.com/goauthentik/authentik/issues/4097

Contributor guide

Open the contributing guide

Research direction

Start with the linked issue #4097 and the referenced 2025.10 release note and OAuth email-scope documentation to understand the removal and current custom-scope workflow. Define the intended built-in verification behavior and its acceptance criteria before locating the affected OAuth scope-mapping entry points; done means applications can obtain verified-email data without custom configuration.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authentication, authorization
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.