Using HTTP Client for User Management

[hiranya911]

In #60 we changed the user management code to use the auto-generated identity toolkit client instead of the HTTP client. This was a useful an interesting experiment that yielded some positive results in the short term. But I feel in the long run it has caused a couple of issues:

1. The auto-generated clients are not updated regularly, preventing us from launching new APIs at the pace we want.
2. We lose control over the transport layer, which makes it difficult to implement optimizations like retries in a single location.

Therefore, I'd like to consider going back to the HTTP client for user management. We can do this in steps:

1. Refactor the user mgt code and implement the currently missing APIs (e.g. session cookie management) on top of HTTP client without changing the existing APIs.
2. Incrementally migrate the existing user management APIs to also use the HTTP client.

@chemidy what do you think?

[google-oss-bot]

This issue does not seem to follow the issue template. Make sure you provide all the required information.

[chemidy]

I think this is a useful, we can deliver new functions very quickly 👍

[hiranya911]

We launched session cookie management API using this mechanism. I'll work on getting other APIs migrated as well.

[canhlinh]

@hiranya911 I've a question. Does firebase support GRPC for sending notifications ?

[hiranya911]

It probably does. @chong-shao should know more.

[chong-shao]

For v1 send API, currently it does not support gRPC.

[canhlinh]

@chong-shao Is there any API version are supporting gRPC ?

[chong-shao]

Hi @canhlinh, as far as I know there is no version that supports gRPC for now.

[canhlinh]

@chong-shao Thanks