More flexibility around the FusionAuth hosted backend

[dan]

We're using the FusionAuth hosted backend but want some more flexibility around the cookie names, domain and expiration times.

What is the best way to get that? File an issue? Raise a support ticket?

[dan]

The hosted backend is designed to cover a number of use cases, but is not very configurable.

If you need more control over the backend, it's suggested you stand up your own application backend to do the token exchange and set the cookies or otherwise store the access token. Many frameworks will take care of this for you.

FusionAuth has provided a sample express application that has the same functionality as the hosted backend and can be extended. For example, to change the domain of the cookie set, you can modify the cookie setting code here.