Hi there! I am integrating my appwrite cloud backend with FlutterFlow using REST. I can log in and use the X-Fallback-Cookies header with the session cookie to perform operations on the appwrite backend. However, looking at the docs, for the REST platform, all requests headers are authenticated with a JWT token - since these have a validity of just 15 minutes according to the docs, I would need to either stay with my current X-Fallback-Cookies implementation or retrieve new JWT tokens before every request. Even the JWT token retrieval is authenticated with the Fallback session cookie. I am afraid that with future updates the X-Fallback-Cookie method might stop working and I will get in trouble with my app. Any advice?
IMO your approach is fine for the time being. There's growing support for long-lived (custom expiry tume) JWTs which will probably be released in an update in the future. Basically, I don't think you have to worry about cookies being deprecated anytime soon. Take it with a grain of salt because I'm not on the core team
Recommended threads
- Appwrite Cloud Services. getting 500 Int...
I'm not able to access any appwrite services on appwrite cloud website, getting a 500 internal error on all services even though status.appwrite.online says the...
- [FEAT REQ] Bun runtime support
Instead of just Nodejs, it would be helpful to also add support for the Bun runtime which can speed up deployments by a ton.
- [ENHANCEMENT] Use the custom Next.js dep...
Deployment adapters on Next.js are now stable! This means that we don't have to stick to the limitations of sniffing out build outputs and manually moving or mo...