Authentication
The IMS Session manager supports several authentication methods by which a connecting client can identify themselves.
You will need to reach out to the IMS team in order to request each of these to be configured for each of your projects.
We currently support the following player auth providers and more can be added upon request.
API Key
If you are still in development and want to try IMS session manager, but haven't implemented player auth yet, we can provide an API Key which you can use for testing purposes.
This should not be used in production or for any public play-tests and is only intended for evaluation purposes.
PlayFab
Authorization: Bearer secret-token:playfab/<session-ticket>
You can use the game client's PlayFab session ticket with the IMS session manager as a means of authorization.
Your game client should provide its PlayFab session ticket within the Authorization header of any API calls it makes to session manager, prefixed with Bearer secret-token:playfab/.
For example, if the session ticket was ABC123DEF456, the authorization header would be:
Authorization: Bearer secret-token:playfab/ABC123DEF456
Accelbyte
Authorization: Bearer secret-token:accelbyte/<authentication-token>
You can use the game client's Accelbyte authentication token with the IMS session manager as a means of authorization.
Your game client should provide its Accelbyte authentication token within the Authorization header of any API calls it makes to session manager, prefixed with Bearer secret-token:accelbyte.
For example, if the authentication token was eyJhbGciOiJIUzI1NiJ9.eyJjbGllbnRfaWQiOiIyMTAzY2JjODJiMjQ1OWJjYWM2ZmEzMDc0MzJiZjA2ZSJ9.TSuoJo1RrSM3n17JVaV75cuEtPIYC7DZPVissbNBabU, the authorization header would be:
Authorization: Bearer secret-token:accelbyte/eyJhbGciOiJIUzI1NiJ9.eyJjbGllbnRfaWQiOiIyMTAzY2JjODJiMjQ1OWJjYWM2ZmEzMDc0MzJiZjA2ZSJ9.TSuoJo1RrSM3n17JVaV75cuEtPIYC7DZPVissbNBabU