The Problem
A wrapper game API using PlayFab ids as the "UUID" in its database, is forced to use the client authentication routes for logging in players:
The /Client/
route offers "platform secret" authentication for all platforms:
https://learn.microsoft.com/en-us/rest/api/playfab/client/authentication?view=playfab-rest
The /Server/
route only offers "platform secret" authentication for Xbox:
https://learn.microsoft.com/en-us/rest/api/playfab/server/authentication?view=playfab-rest
Why using /Client/LoginWith[Platform]
in the wrapper API is bad:
You can get rate-limited on server.
You can't disable client API access for your title.
/Server/LoginWithServerCustomId
isn't a valid option:
When using Playfab ids as the "UUID" in your database
When you use the Standard plan
Feature Request
Add all the "platform secret" authentication methods from the /Client/
to the /Server/
route.