Request to add/link new provider to the account results in 501

[Junaid-Ahm]

[REQUIRED] Environment info

firebase-tools: 10.20.0

Platform: Ubuntu 20.04 x86_64

[REQUIRED] Test case

This issue is only happening in emulator. Works fine with actual firebase project.

{
  "error": {
    "code": 501,
    "message": "linkProviderUserInfo is not implemented yet.",
    "errors": [
      {
        "message": "linkProviderUserInfo is not implemented yet.",
        "reason": "unimplemented"
      }
    ],
    "status": "NOT_IMPLEMENTED"
  }
}

[REQUIRED] Steps to reproduce

1. Create an account in emulator (eg via firebase admin SDK's create user)
2. Attempt to add/link new provider to the existing account via update user (eg via firebase admin SDK's update user), which makes the POST request to endpoint /accounts:update results in the above error.

[REQUIRED] Expected behaviour

Should add/link the provider info to the account.

[REQUIRED] Actual behaviour

Returns error with above error message.

[yuchenshi]

Hi, thanks for filing this issue! We are unable to promise any timeline for this, but if others also have this issue, adding a +1 on this issue can help us prioritize adding this to the roadmap.

(Googler-only internal tracking bug: b/222142440)

[yuchenshi]

FYI, we're also accepting Pull Requests for this feature. A good place to start is

firebase-tools/src/emulator/auth/operations.ts

Line 977 in daa604a

"linkProviderUserInfo",

[Junaid-Ahm]

@yuchenshi any plans for this?

[Junaid-Ahm]

@prameshj Can you also please review this and raise an internal ping for a followup?

[prameshj]

@malcolmdeck

[Junaid-Ahm]

@malcolmdeck Looking forward to your thoughts on this?

[christhompsongoogle]

We're aware of the issue but don't have a timeline on a resolution.

[NateMay]

Are there any other mechanisms to seed users in the emulator with providers linked? I can't seem to set provided data with createUser() or updateUser() so my team is currently forced to manually link providers within the UI.

[Junaid-Ahm]

@yuchenshi @christhompsongoogle @prameshj @joehan still waiting a timeline on this - opened in Feb'22

[christhompsongoogle]

Thanks for following up, but I have no updates to share. The fastest way to get this resolved would be to try your hand at a fix via Yuchen's link above.

[paulrostorp]

I've implemented this as suggested by @yuchenshi in #6291.
I've published it to npm here as @paulrostorp/firebase-tools