I have this function and I will use the set jwt token. Now the client side will pass a jwt token for that cloud function I want answers for all this questions:
- In server side if I account.get. I can get the user info even I am in the server side right?
- I am going to create documents and set a permissions to the specific user, not himself/herself. Because in client side when I try to set a permission to referred to another user it gives me an error, so In server side can I able to do this ?
I can't parse the first part of your question, but the 2. - yes if you have a privileged API key.
But then it also works from the client
I will use jwt token insteaf using the api key.
I am getting error when I am creating permission specific user excluding self id, for example User B will have permission to write this document. IN that case it will throw an error
But nvm
Using a JWT is the same as making the API call client side as the user.
If you want to set permission to someone else, you must use an API key
Btw, the client doesn't need to pass a JWT. If they're logged in and they execute function, 2 headers are automatically populated with the user's id and JWT. See the docs.
Yes, calling account.get() with a JWT will get that user.
Why do you need to call account.get()?
Just nothing heheh just want to clarify. Btw, does the team will implement that allow us to to set permission to someone else in the future or not?
Probably not
Recommended threads
- Attribute not found in schema on REST AP...
I'm querying a appwrite collection via the REST API on appwrite cloud 1.9.5 (no SDK) via a cloudflare worker and keep getting: ``` {"message":"Invalid query: A...
- Quota not resetting
hi, im using appwrite's free tier plani hit my read limts last month and the billing cycle said it would reset on june 4th but that is today, the billing cycle ...
- Request for temporary 3 to 4 hours datab...
Hi Appwrite Team, I hope you are doing well.We are an early-stage startup currently running on Appwrite Cloud. We have unfortunately exhausted our database rea...