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.

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

Enforce a verified email via OIDC auth #2376

Closed
jobannon opened this issue Jul 19, 2023 · 2 comments
Closed

Enforce a verified email via OIDC auth #2376

jobannon opened this issue Jul 19, 2023 · 2 comments
Labels
duplicate This issue or pull request already exists

Comments

@jobannon
Copy link

jobannon commented Jul 19, 2023

Enforce a verified email via OIDC auth

Problem

The OIDC protocol allows for a claim email_verified. This proves that the user has verified their email in accordance with this federated partner's requirements (typically, this is the user clicking a link from their inbox). When FusionAuth is the SP, sometimes you only want to allow federation and user creation for users that have proven they have verified their email and own their email address.

Solution

We should offer an IdP configuration that prevents automatic linking and user creation unless this claim is present.
linking-strategies

Alternatives/workarounds

Manually create a user link using our Link API to only link one a user has a verified email address or meets other requirements.

This will only work if the IdP in question uses the email_verified claim when they are the IdP and FusionAuth is the SP.
Internal - 73727

Community guidelines

All issues filed in this repository must abide by the FusionAuth community guidelines.

Related

How to vote

Please give us a thumbs up or thumbs down as a reaction to help us prioritize this feature. Feel free to comment if you have a particular need or comment on how this feature should work.

@mooreds
Copy link
Collaborator

mooreds commented Jul 28, 2023

Could also update the lambda docs to show that.

@robotdan
Copy link
Member

Looks like we duplicated this via #2423.

@robotdan robotdan added the duplicate This issue or pull request already exists label Oct 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

3 participants