GitHub App Login Failure with Missing Permissions and Absence of Public Email

Open
#7,777 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
github, nextjs, typescript
Domain
authentication

Research direction

Start by reproducing the GitHub App login with no permissions and no public email, then trace the Prisma Adapter path that produces the missing-email error and OAuthCreateAccountError. Done means the missing permission or email condition produces a distinct PermissionMissing or EmailMissing error in both server and client behavior.

Written by the indexing model from the issue text.

Description

enhancement triage
Description 📓

When the "Account permissions -> email addresses (read)" permission is not granted, Next.js Auth throws an error (with the Prisma Adapter) indicating that the email address cannot be found. Additionally, a client-side error occurs (OAuthCreateAccountError). It would be beneficial for Next.js Auth to throw an error named "PermissionMissing" or "EmailMissing" instead.

How to reproduce ☕️

Create a GitHub App without setting any permissions, and then attempt to log in using Next.js Auth. Ensure that you do not have a public email associated with your GitHub account.

Dominant language
TypeScript
Stars
28.4k
Forks
4k
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nextauthjs/next-auth

All issues in nextauthjs/next-auth

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.