3 ms·
Thank you, that was exactly the point that I was missing! I was only looking at the communication between front end back end which i both own. Thanks to you, I
by Draken93 6y ago
Thank you, that was exactly the point that I was missing!
I was only looking at the communication between front end back end which i both own. Thanks to you, I now understand my wrong way of thinking.
Would you consider this way of explaining it as correct:
If I look at it from another perspective it is pretty much like the normal oauth use case. By trusting Auth0/Okta I share my users and the backend access with them.
Since the frontend is 3rd party to Auth0, it is like the normal use case: They provide a application(my frontend) the permission to get access to "their" users data and to commit actions on behalfe of "their" users.
To be honest: Secretly I was hoping for you to answer, as I know that you are activ on HN ;). Your articles are under the best ressources I found on this topic. I espescially like your 2part series on session management!Thanks for your work for the community! I also looked into SuperTokens and find it very promising as I believe that it is extremly important to adress the problem of token theft. In the future that will be crucial as other attacks get less promising due to more secure websites.
I am still a student and I am currently working on my thesis. My target is to create a full-stack data management plattform for the company I writing my thesis at. (I do this completly on my own.) The plattform will be accessed over a SPA.
As you can probably imagine that is a not a easy task without having done something of this size before.
I want to do it right from the ground of. I want the plattform to be scalable, maintainable and secure.
I already read tons of articles, books etc. But I am still looking to improve my knowledge to make no mistakes that i realize while Implementing the plattform.
On the same time, I have to look into ways to outsource work where it is possible. Otherwise I don't think I am able to deliver in time. My application requires User management, and role dependend authorization as well. How big do you consider the overhead of using Supertokens and implementing the user management on my own, to just using Auth0/Okta? I really love the additional security that SuperTokens provides. But If I am unable to deliver in time, thats pretty much worth nothing.
Excuse my many questions please. You have my understanding if you do not have the time to deliver this kind of support on HN.
- advaitruia 6y ago> "Would you consider this way of explaining it as correct.." Yes, that is correct. Ideally, for the most secure setup, you should use the authorization code grant flow - which would involve your backend gaining access to Okta / Auth0 rather than your frontend. But yes, many people use the default setup which involves their own frontend having access to the user's info on the IdP. The default setup may also involve using localstorage with Auth0 (which we do not recommend - as do many other bodies such as OWASP and NIST). Glad you liked our articles! > In terms of implementing user management: We provide the ability the following user management functions: - Loop through all users - Ban / unban via session revocation - Adding / modifying user roles to session and fetching them in a backend API (post session verification) and frontend What we don't have: - A UI to manually see / edit the info mentioned above - Delete user functionality (we plan to add this) So if you can do without the things we don't have, then it shouldn't take much time for you. Feel free to join our Discord at supertokens.io/discord if you like!
- Draken93 6y agoThank you for your time, your answers really helped me out!