supertokens-core icon indicating copy to clipboard operation
supertokens-core copied to clipboard

Types of customisations users might need (override feature)

Open rishabhpoddar opened this issue 3 years ago • 1 comments

  • Custom user IDs for users / Using their own format of userId since all their other tables expect that format.
  • For users who had signed up already, the sign in API should query their logic / db, and for other users, it should query SuperTokens.
  • Overriding our session management solution to change how tokens are stored on the frontend (within a shopify app).
  • Overriding a react component in our UI to change how the UI looks (to hide the sign up button). Likewise, overriding our sign up API to disabling sign up. So that only the admin can make an account.
  • Adding third party account consolidation feature whilst we don't support it
  • Modifying emails that are used to sign up / in (overriding the sign in / up API) to add a tenant ID to the email for multi tenancy, with one user pool.
  • Sending post sign up notification to slack by overriding the sign up API. The user wanted to access the actual request headers to get info about the device / IP.
  • Keeping track of tokens for other services (faunaDB or Hasura) in the supertokens session
  • Allowing only work emails to be used while signing up.
  • Post session verification, update some shared data structure to mark the user as online
  • Adding recaptcha to the sign in / up form.md
  • Do not login a user post sign up - instead redirect them to the login screen
  • Adding a logo to the sign in / up screen
  • Allowing users to sign in only if they use a specific app on the frontend, else not.
  • Adding custom form field input to the session during sign in / up.
  • Sign in account lockout if failed to sign in too many times (https://gist.github.com/rishabhpoddar/6fe2b98ac1e09aafcba4a7307027097e).
  • Prevent creation of session post sign up and only do that during sign in
  • Associating different login types with the same account. For example, using email / password for end users, but magic links for customer support team people (to login to those same user accounts)
  • Allow multiple emails to be user per user when signing in
  • Step up authentication
  • Custom email / SMS content.
  • Using whatsapp or other services to send SMS content instead of using SMS

rishabhpoddar avatar Jun 02 '21 13:06 rishabhpoddar

It would be very useful if it is finally done. I leave here a code fragment for the "Adding custom form field input to the session during sign in / up." use case made in Django

Code: image

Signup form: image

Dashboard result: image

jalvarezz13 avatar Oct 15 '23 11:10 jalvarezz13