kstulgysOriginal post
Rank 2: Process
I deployed appwrite function that returns user jwt:
module.exports = async function (req, res) {
const jwt = req.variables.APPWRITE_FUNCTION_JWT;
res.json({ jwt });
};
When triggered through admin api I can see jwt in the logs, but when triggered in my app (locally) serverside I see jwt as empty string:
let token = await functions.createExecution('getCurrentUserJwt');
// token object:
{
token: {
'$id': '6494abfd1dcc5d578e3b',
'$createdAt': '2023-06-22T20:15:57.122+00:00',
'$updatedAt': '2023-06-22T20:15:57.129+00:00',
'$permissions': [],
functionId: 'getCurrentUserJwt',
trigger: 'http',
status: 'completed',
statusCode: 200,
response: '{"jwt":""}',
stdout: '',
stderr: '',
duration: 0.0022101402282714844
}
}
Why is this? Appwrite is deployed to digital ocean.
Summary
The user is trying to call an "appwrite" function but is not receiving the expected response. They mention that the variable APPWRITE_FUNCTION_JWT will only have the JWT when the function is executed from a client-side or from a server-side using JWT instead of an API token. They discuss the idea of maintaining the user's JWT server-side without passing it from a cookie and initializing the server-side SDK using the JWT. They mention triggering a Next.js API endpoint and executing the function server-side. The user mentions that when the function is triggered through the admin API, they can see the JWT in the logs, but when triggered in their