关于Firebase Auth自定义令牌中some-uid的取值及第三方社交登录后控制台显示的技术问询

Great questions! Let’s break this down clearly for your custom social login use case:

What should I use for some-uid? #

The uid parameter in createCustomToken() needs to be a unique, non-reusable string that identifies the user in your system. Here’s what you should keep in mind:

• It can be any string (up to 128 characters) that’s unique across all your users. Common choices include:
  • A UUID generated specifically for this user
  • The user’s ID from your existing backend database (if you have one)
  • A unique identifier from the custom social provider you’re integrating (like their user ID from that platform)
• Critical rule: Never reuse this UID for another user. Firebase uses this UID as the primary key for the user’s auth record, so duplicates will cause conflicts and break user sessions.

Will users created with custom tokens appear in the Firebase Auth console? #

Absolutely! When a client signs in using the custom token you generate, Firebase automatically creates a full user record in your project’s Auth console—just like users who sign in with Google, email/password, or any other supported provider.

This record will:

• Have the exact UID you specified in the custom token
• Show up in the "Users" tab of the Firebase Console alongside all other auth users
• Support all standard user management features (updating profile info, disabling accounts, setting custom claims, etc.)
• If you want to add additional details (display name, email, profile photo), you can use the Admin SDK’s updateUser() method right after generating the token, or sync those details after the user signs in on the client.

A quick tip for your flow: Once the user signs in with the custom token, you can also link their Firebase auth record to other providers later using linkWithCredential() if needed, but the initial record will be fully valid and visible in the console from the moment they first sign in.

内容的提问来源于stack exchange，提问作者dontknowhy