hello, I want to ask, can we run supertoken with our own ui design, not ui default ?

Hi, how do I redirect my page to login page in a backend route protected by verify_session. I am using Flask and Plain JS frontend. So if a user navigates to domain.com/account , if session is not valid, I'd want to redirect to /login . Right now, I just get a "{"message":"unauthorised"}" with 401 response.

Hi, How can i prevent the input field from changing its background on focus? (React) I have set the following styles in ThirdPartyEmailPassword:

inputWrapper: {
  backgroundColor: 'var(--input-background)',
  borderColor: 'var(--input-border)'
},
input: {
  color: 'var(--text-color)',
}

I found an edge case in our Auth0 to SuperTokens migration. Users that do not yet exist within SuperTokens might have forgotten their passwords. So we need a way for creating their supertokens account upon doing a password reset request 🤔 What I have in mind is the following: 1. Overwrite

getUsersByEmail

2. Do a RPC call to our services/auth0 for checking whether an email/password user with a given email exists 3. if he does not exist use

originalImplementation.emailPasswordSignUp

for creating the user with a random password 4. return that newly created user from the

getUsersByEmail

function I think one problem here is that

getUsersByEmail

is not exclusively used by the reset password functionality - I can observe that function being called for a basic login attempt as well. 🤔 As I workaround I figured out that using the

userContext

might work - though it seems a bit like an hacky attempt.

...
async getUsersByEmail(input) {
  // In case this does not happen as part of the reset password token flow we just use the default implementation.
  if (
    input.userContext?.['_default']?.['request']?.['original']?.['url'] !==
    '/api/auth/user/password/reset/token'
  ) {
    return originalImplementation.getUsersByEmail(input);
  }
 ...

Does that seem reasonable? Are there any better alternatives? Did anyone do something similar before?

Hi, I was trying to integrate SuperTokens auth api into my angular project by navigating through quick setup guide in the documentation, however after adding express i noticed that my apped stopped building. I'm constantly getting getting errors such as the one in attachment. Could someone help me resolve this issue? Thanks in advance for any help/tips

Last question for today 😅, how can I configure my SMTP with username/password credentials ? I can't find a way to give the username

Hello! We have a little problem about implementation of Supetokens on Ionic/Capacitor. In particular about the native versions of it. Its like if the back-end side doesn't allow customScheme (ex: capacitor://app.id/home). After the basic implementation of docs we have this error on iOS: Unhandled Promise rejection: – "Please provide a valid domain name" Can some help me please? Thanks in advance!

Is it possible to disable cors fully for testing? I’m getting an error saying that wildcard can’t be used when credentials mode is ‘include’

Hi, was wondering if SuperTokens has a SOC 2 report available somewhere? I see there's a trust page at security.supertokens.com, but couldn't find the SOC 2 report.

Hi, has anyone tried using SuperTokens with HTMX? If so, do you have any guidance or advice?