user logins -> i create session token on server side -> i create cookies
Then i'm using the following code to create an appwrite session based on the session token & protect my frontend routes.
But now I want to protect my api routes, what is the best approach? Since the token can be changed on the client side, how do I verify the integrity of it ?
export async function createAppwriteSessionClient() { const client = new Client() .setEndpoint(process.env.APPWRITE_ENDPOINT) .setProject(process.env.APPWRITE_PROJECT)
const session = cookies().get("session"); if (!session || !session.value) { throw new Error("No session"); }
client.setSession(session.value);
return { get account() { return new Account(client); }, }; }
Should I call createAppwriteSessionClient() everytime before making any requests to appwrite? assuming client.setSession(session.value) will reject tampered session tokens?
Recommended threads
- rxdb integration code not working
https://appwrite.io/blog/post/offline-first-journal This code does not work with rxdb and appwrite packages set to february releases nor newest releases
- Costom domain Issues
Hi Appwrite team We’re having issues verifying a custom domain. We added the required CNAME and CAA records to our DNS provider and waited for at least 2 days a...
- No domain visible after creating functio...
Saw this in docs yet i have no domain (Pro): ``` Generated domains In the Appwrite Console's sidebar, click Functions. Under the Domains tab, you'll find the g...