Yes. I'm afraid that will be necessary at the moment because: - We do not expose the JWKs in a format like auth0's - The JWT signing keys keep changing automatically (without logging anyone out) for enhanced security.

Some questions: - What made you want to switch from auth0 to using us? - What type of auth do you want? email password / social login / something else?

Amazing! Thanks for the help.

Still not decided to move. We are evaluating Supertokens now, but we were already considering to move out of Auth0, but originally to Cognito, then I stumbled upon you guys and decided to take a look. I was really impressed with the easy of use after testing out Blitz.js over the weekend. Mainly what I consider the biggest issue is that Auth0 adds too much complexity on things we need simple, plus, it's expensive. For an early stage startup I don't think we should be spending too much cash and time on auth, but this is the reality. And finally, the complexity of customizing the login/registration screens are simply TOO annoying. We have been using both email password + social login. Also OTP would be one thing to look for the future (not exactly now).

Understood! How did you stumble upon us? From blitz.js?

Yes!

great! thanks. Please feel free to ask more questions here. I'd be very happy to help out.

Thanks a lot! I'll post here if we make a change later on. 🙂

I know it's late for you guys, but is there anyone available to help?

hey @User . We are available for help now.

it was almost 1 am at the time of your message.. haha

Hi! I just started using SuperToken for a school project. One of the requirements I have is to be able to delete the account of a user. However, I couldn't find any mentions of a way to delete a user. I'm using the managed service, node sdk, react sdk and ThirdPartyEmailPassword recipe. Is it possible to delete a user using this setup?

hey @User . We do not have a delete user functionality at the moment. We will be working on it soon. As a temp hack, you could create your own table called "deleted_users" and store userIDs in that. So when deleting a user, you should insert their userId in that table, and revoke all their sessions. Furthermore, during login, you should check if a user has been deleted, if yes, then do not allow them to login. This would require you to disable the default login API and create your own manually (using our code), but add one extra step to it. I will be happy to guide you through this (is simple to do). A question: What made you want to use supertokens?

Thanks for your answer. I will check if this could work. The teacher will also check the code, so I have to make sure it satisfies the criteria. To answer your question, I've known supertokens for a few months now and wanted to try it. I like to try new tools in my school projects since they usually aren't very big. I've used Auth0 in the past, but I like the idea of an open-source alternative. So I decided to give it a try. As a first impression, I like a lot the security it provides out of the box, but I found the doc hard to navigate between sdk doc, tutorials for recipes and overall concepts.

Okay understood. Thanks for the feedback. Did you have to navigate across the nodejs docs and the thirdpartyemailpassword docs? Or did you find navigating between pages in thirdpartyemailpassword docs hard?

Between the nodejs and thirdpartyemailpassword. I think it was because I wasn't able to access all the doc in the navigation. I was always wondering if I missed a part of the doc since some part could only be accessed from a specific page (like sdk doc and recipe doc).

hmmmm. Would you have any ideas on how we can improve it further please?

Sorry for the time it took. I'm trying to pinpoint exactly what was the problem, but it's hard to say. The only thing I can think about is having all the doc accessible from any pages, but it might overload the navigation, so I don't really know.

Okay! thank you for the feedback!

Hi, I am trying to implement supertokens on Laravel project where it will receive api request from mobile app. I have managed to setup supertokens. I am able to create session and it is stored in DB, I have access and refresh tokens. How do I send access token to server and get verified via supertokens middleware. Do I have add to cookie header or authorisation headers. I have tried to look for an answer in docs, but is not mentioned there, at least I couldn't find it.

hey @User are you using react-native? iOS or android?

depending on that, you will need to use our frontend SDK which will handle the cookie management and refreshing for you. Please refer to the docs: - android: https://supertokens.io/docs/android/installation - iOS: https://supertokens.io/docs/ios/installation - react-native: https://supertokens.io/docs/react-native/installation

@User I am using flutter. How can I handle cookies and refreshing manually?

Oh I see. You will need to see if flutter supports cookies or not first.

it does

If it does, the session flow is as follows (at a high level): - You will want to save the access and refresh tokens in the cookie store on login. - For each API request, you will need to send the access token as a cookie. This should ideally happen automatically. - Once the access token expires (you get a 401 response from an API). You will need to use the refresh token to call the refresh API (again, the refresh token cookie will go automatically since its path matches the refresh API's path). - If the refresh is successful, you will have a new access token and call call the original API again. Else, your session has expired and the user will need to login again. The above is a very high level flow. There are locking related nuances that you will have to consider whilst calling the refresh API to prevent false negatives alerts of token theft. I suggest that you see our react native SDK's source code and try and copy that as much as possible. If you do end up making it, then we would appreciate a PR to support flutter 🙂 React native SDK's code: https://github.com/supertokens/supertokens-react-native

Specifically, the code is: https://github.com/supertokens/supertokens-react-native/tree/master/lib/ts

Thank you for explanation, I will look into that

In case you want to contribute, you can create a PR here: https://github.com/supertokens/supertokens-flutter