Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

`generateVerifyAndChangeEmailLink` only works for accounts with existing email

Open
#2,826 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
firebase, node.js, typescript

Research direction

Start by tracing generateVerifyAndChangeEmailLink in the Firebase Admin Node.js authentication implementation and its existing tests, using the reported call with a user lacking an email as the reproduction case. Done means the link can be generated for such an account while email enumeration protection remains enabled, with coverage for the reported scenario.

Written by the indexing model from the issue text.

Description

api: auth
  • Operating System version: Firebase Cloud
  • Firebase SDK version: 12.6.0
  • Firebase Product: auth
  • Node.js version: 20
  • NPM version: 10
Steps to reproduce:

In our app, we allow social login with Facebook (and more, but irrelevant). When authenticating with Facebook, the user can decide to not provide his email address. Since our whole application builds arounds mails, we ask them to provide one.

We activated email enumeration protection recently!

Since we can no longer set that mail in the frontend code and we want styled/custom mails, we would like to use generateVerifyAndChangeEmailLink in the admin library. But it seems impossible to call that function, if we don't provide an existing email.

This is, how the user looks in Firebase Console

Image
Relevant Code:
// I tried different things for the existing mail, but all failed
await getAuth().generateVerifyAndChangeEmailLink('-', email, actionCodeSettings);
Dominant language
TypeScript
Stars
1.7k
Forks
419
Avg merge
4d 20h
Merged PRs (30d)
16

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 firebase/firebase-admin-node

All issues in firebase/firebase-admin-node

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.