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
- start the auth emulator with
firebase emulators:start --export-on-exit=./users --import=./users
- Serve this file locally.
- Follow steps to reproduce
[REQUIRED] Steps to reproduce
- Start the auth emulator with
firebase emulators:start --export-on-exit=./users --import=./users
- Using the provided web ui with firebase auth emulator running, create a user via the Google Provider button.
- 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.
- Stop the emulator via
SIGINT (ctrl+c)
- 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.
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
firebase emulators:start --export-on-exit=./users --import=./users[REQUIRED] Steps to reproduce
firebase emulators:start --export-on-exit=./users --import=./usersabc-123and not the default tenant.SIGINT(ctrl+c)[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.