Important Security Changes Coming To ClientCallable In Upcoming Release 1.2

The team at Beamable puts security first and foremost when we work on upcoming releases and we are making a change in how the ClientCallable function works in our upcoming 1.2 release.

Starting in 1.2, if you use ClientCallable you will need to ensure that all requests have a valid Authorization header, or else your request will not work anymore and fail with a 401 or 403 error. This is especially important if your project uses third-party webhooks as those requests will now need to be made using the new Callable function added in 1.2, which replicates how ClientCallable used to work.

If you are only using Beamable Microservices from within a Unity game client, this change should not affect your game in any way.

If you have any questions regarding any of the above or concerns about how this might effect you, please contact us at support@beamable.com