Firebase auth emulator in multi-tenant mode only exports users tied to the default tenant

[damoonrashidi]

When using the auth emulator in a multi-tenant setup, users aren't exported or imported for any tenant other than the default tenant.

[REQUIRED] Environment info

firebase-tools: 11.24.1

Platform: macOS

[REQUIRED] Test case

1. start the auth emulator with firebase emulators:start --export-on-exit=./users --import=./users
2. Serve this file locally.
3. Follow steps to reproduce

[REQUIRED] Steps to reproduce

1. Start the auth emulator with firebase emulators:start --export-on-exit=./users --import=./users
2. Using the provided web ui with firebase auth emulator running, create a user via the Google Provider button.
3. See that the tenant is available in the tenant select dropdown in the emulator auth UI, and that the user is listed for tenant abc-123 and not the default tenant.
4. Stop the emulator via SIGINT (ctrl+c)
5. See that the exported user json file does not include the user that was available in the emulator UI.

[REQUIRED] Expected behavior

The exported users should include all users, segmented by tenant.

[REQUIRED] Actual behavior

The exported users only include users tied to the default tenant.

[edupsousa]

I don't know if it's related but since a few days ago we noticed that users created in other tenants than the default using the Google Auth Provider are not being listed in the popup sign-in screen.

[KennyBZA]

This bug is still present on current version.

Environment:
firebase-tools: 12.4.2
Platform: macOS

[damoonrashidi]

I would try to submit a fix for this myself but it feels like it could potentially be a breaking change to change the format of the exported users and I don't want to take that liberty.

I have a local workaround where generated test users are stored in a json that looks like this

{
  tenantId1: [user1, user2],
  tenantId2: [user3, user4]
}

And then another script that goes through that json and seeds the local emulator with the users for each tenant, but of course that script needs to be run every time the emulator is started which is pretty annoying.

[mikenigels]

I have a project suffering from this issue as well.

@damoonrashidi is the workaround you came up with something you can share with the community? I was just about to develop a similar set of scripts while waiting for an official fix, when I found your post.

[damoonrashidi]

@mikenigels I've created a gist here with the majority of the code. It's not anything pretty, I just hacked it together under the assumption that an official fix will come sooner or later.

I have it in a file called seed-users.ts that I run via yarn seed:users that is an alias for

export $(cat env/local.env | xargs) && ts-node -r tsconfig-paths/register ./database/seeds/seed-users.ts"

It's not an open source project so I can't share all of it unfortunately, but I am one of the owners so I tried to share as much as possible. Let me know if you run into any issues

[steveoh]

This would save me some time in my development loop. Please consider this a priority.