Payload may contain padding(=) when creating custom token.

[firebase]

Payload may contain padding(=) when creating custom token.

[google-oss-bot]

Hey there! I couldn't figure out what this issue is about, so I've labeled it for a human to triage. Hang tight.

[google-oss-bot]

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

[hiranya911]

This is not likely to get fixed. Why are you even trying to decode custom tokens on your own? They are only meant to be passed along to the Firebase Auth servers via a signInWithCustomToken() call.

[IZAQI]

Thank you for your reply.

I understand that I can sign in by calling signInWithCustomToken ().
Currently avoiding errors by calling signInWithCustomToken ().
I asked a question to judge whether this error avoidance should be adopted as a formal process.

In my system, multiple databases work together with Firebase users as keys.
Therefore, I do not necessarily need to sign in to Firebase.
Since it is assumed that the load becomes instantaneously high, if only the target user is required in the REST API, I decode it myself.
There was concern that sign-in and sign-out would be repeated in parallel.
Is it reasonable to use signInWithCustomToken () even under such circumstances?

---

This sentence translated Japanese into English using Google Translate.

[hiranya911]

It's very difficult to understand your specific question or use case from the translated description. In general, you should never mint a custom token, unless you're planning to sign in with it in a client-side app (Web, Android or IOS). That's all they are good for. If you just need to pass a uid to a client app, I'm sure there are other easier ways for that.

[LeonardoRick]

does this library have a signInWithCustomToken() vesion in python? I'm trying to connect a client python application

[hiranya911]

This library doesn't provide any client-side APIs at the moment.

[LeonardoRick]

@hiranya911 thanks. Any suggestion to achieve my goal?

[hiranya911]

You can try the REST API: https://firebase.google.com/docs/reference/rest/auth#section-verify-custom-token

Requires a web API key to access.