SuperTokens is an open source authentication solution offering features like: Different types of login: Email / password, Passwordless (OTP or Magic link based).

SuperTokens.com

So let’s say a web application with user authentication needs to store certain details like address, phone number, etc. I’m assuming it would be typical to authenticate with SuperTokens and then store the extra user information in the web app’s own database, correct?

If that is the case, what’s the benefit of storing role info in SuperTokens as opposed to using one’s own database?

1) it saves you time to write those extra queries

2) it integrates well with our user roles claim which adds role information in the session automatically. You can modify the user roles recipe to read from your db and then this would work too, but that’s an extra customisation