starred/documenso

Fork 0

mirror of https://github.com/documenso/documenso.git synced 2026-04-25 22:05:59 +03:00

[PR #856] [MERGED] fix: auto verify google sso emails #1211

New issue

Closed

opened 2026-02-26 19:32:18 +03:00 by kerem · 0 comments

kerem commented

2026-02-26 19:32:18 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/documenso/documenso/pull/856
Author: @dguyen
Created: 1/23/2024
Status: ✅ Merged
Merged: 1/25/2024
Merged by: @dguyen

Base: main ← Head: fix/auto-verify-google-emails

📝 Commits (3)

9031fe7 fix: auto verify google sso emails
b28b43c Merge branch 'main' into fix/auto-verify-google-emails
472fa60 fix: set correct identity provider

📊 Changes

1 file changed (+18 additions, -1 deletions)

View changed files

📝 packages/lib/next-auth/auth-options.ts (+18 -1)

📄 Description

Description

Currently logging in via Google SSO will still require you to verify your email. This shouldn't happen since going through Google SSO implies you have access to that email.

Changes Made

This change resolves that by setting the emailVerified attribute in the database when you access the application via Google SSO.

This also updates the identity provider for users who log in through Google to have it correctly set as GOOGLE.

Testing Performed

Logged in via SSO and no email verification was requested
Logged in via non SSO and email verification was requested

Checklist

I have tested these changes locally and they work as expected.
I have followed the project's coding style guidelines.

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/documenso/documenso/pull/856 **Author:** [@dguyen](https://github.com/dguyen) **Created:** 1/23/2024 **Status:** ✅ Merged **Merged:** 1/25/2024 **Merged by:** [@dguyen](https://github.com/dguyen) **Base:** `main` ← **Head:** `fix/auto-verify-google-emails` --- ### 📝 Commits (3) - [`9031fe7`](https://github.com/documenso/documenso/commit/9031fe7b79a4a41168f2ab3f4d2a320888b39ca4) fix: auto verify google sso emails - [`b28b43c`](https://github.com/documenso/documenso/commit/b28b43cdbe9b022dfbb484aa002d7fa868e87265) Merge branch 'main' into fix/auto-verify-google-emails - [`472fa60`](https://github.com/documenso/documenso/commit/472fa60077b3f211ce18c844c19ce6b6256d2649) fix: set correct identity provider ### 📊 Changes **1 file changed** (+18 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `packages/lib/next-auth/auth-options.ts` (+18 -1) </details> ### 📄 Description ## Description Currently logging in via Google SSO will still require you to verify your email. This shouldn't happen since going through Google SSO implies you have access to that email. ## Changes Made This change resolves that by setting the `emailVerified` attribute in the database when you access the application via Google SSO. This also updates the identity provider for users who log in through Google to have it correctly set as `GOOGLE`. ## Testing Performed - Logged in via SSO and no email verification was requested - Logged in via non SSO and email verification was requested ## Checklist - [X] I have tested these changes locally and they work as expected. - [X] I have followed the project's coding style guidelines. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>

kerem

2026-02-26 19:32:18 +03:00

closed this issue
added the
pull-request
label

kerem referenced this issue

2026-02-26 19:33:26 +03:00

[PR #1211] [MERGED] chore: profiles announce blogpost #1477

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/documenso#1211

No description provided.

Rows
Columns