
I have been seeing multiple implementations of auth across tools like Clerk, Supabase and it seemed like they are using async storage or secure storage as some form of storage mechanism to store some jwt token or something (not super fluent with auth stuff).
I see a function call named account.createSession in Appwrite docs. Is this function responsible to storing some token as well locally on device?
Asking since I want to be super sure the auth works well and is handled well by Appwrite itself and there's left for me to be done beyond what Appwrite functions handle. Thanks!
Recommended threads
- Error while migrating from supabase.
I am trying to migrate my data from supabase top appwrite using their migration tool, but I am getting this error every time: ```{ "$id": "68cdb869bb7bb07d68...
- Suggest simple auth flow using just a cu...
Hi...i wanted to know how can we create a auth session using custom id and password. I can give each teacher and student some specific id and corresponding to ...
- Appwrite realtime stopped working all of...
In our production environment, Appwrite Realtime suddenly stopped working and no updates are coming through , can you confirm if there are any known issues?
