yuvrajOriginal post
Rank 1: Thread
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);
},
};
}
Summary
To validate an existing session token in Appwrite, it is recommended to check the session token's integrity on the server side. You can create a function like `createAppwriteSessionClient()` to set up the client with the session token and protect both your frontend and API routes. This approach ensures that tampered session tokens are rejected. When protecting API routes, always validate the session token on the server side to maintain security.