Skip to content

[FR] Missing MultiFactor property in UserRecord #379

Open

Description

@cperez87

Hi,
The MultiFactor property is missing in the .NET (and Java) implementation of UserRecord.
Other implementations like Go, Python, and Node already have it.

While we wait for it to be added, is there any recommendation to get the raw response returned by the accounts:lookup call?

Thanks

Activity

  1. google-oss-bot commented on Feb 19, 2024

    @google-oss-bot

    I found a few problems with this issue:

    • I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
    • This issue does not seem to follow the issue template. Make sure you provide all the required information.
  2. cperez87 commented on Feb 20, 2024

    @cperez87
    Author

    In the meantime, I ended up creating a custom HttpClientFactory to add a custom DelegatingHandler with a Channel. And subscribe to it to capture the Response content.
    Any other temporary suggestion is welcome.

  3. changed the title [-]Missing MultiFactor property in UserRecord[/-] [+][FR] Missing MultiFactor property in UserRecord[/+] on Mar 11, 2024
  4. Somebodybro commented on Jun 11, 2024

    @Somebodybro

    Hey! I made a fork for this here and started working on this so i'll make a pr when that is done.

    There are some new things I need to do, like adding a list property to userRecordArgs, but that should be fine.

    There should not be any other problem in doing this except adding the fields and making them serialize/deserialize correctly.

    This is my first time contributing to the firebase .net sdk repo, so if you see anything dubious in the fork a bit later, when I've gotten it to works and such, do say something here, so that I can fix it before piling on a lot of work on a misguided version!

  5. Somebodybro commented on Jun 13, 2024

    @Somebodybro

    I created a pullrequest for this!

    #409

    If there is any deeper discussion to be had about it, that cannot be handled within the pr comments, I think that can be had here?

  6. Somebodybro commented on Jul 15, 2024

    @Somebodybro

    @lahirumaramba My pull request has been floating around for a while.
    If there is something wrong with it, i'm more than happy to keep working on it.

  7. Somebodybro commented on May 19, 2025

    @Somebodybro

    @pragatimodi Is there any possibility for this to get furthered? Again, if there is something wrong with the pr, then I'm happy to fix it/change it, but it has been almost a year now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions