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

SuperTokens.com

What's the best way to manage users (updating user information, resetting passwords) when there are many users?

The dashboard doesn't appear to support search and we can't page through 1000s of users…

Hey. What’s the version of the backend SDK that you are using? We do have search on the dashboard via email, phone number, social provider

Ah, interesting OK! We're on 13.1.2 right now

search was introduced in version 13.4.0. You can just upgrade to that, it's not a breaking change. The other thing thats required is that the core has to be of version >= 4.6.0, which we can update for you (once again, not a breaking change)

Is there a particular order we should do things in?

(When you say "core", I'm assuming you mean the server-side code you're running for us, right?)

yea, the managed core thats running on ouor infra

update the core first, then the backend SDK is usually whats recommended.

Alright, well if the core update is non-breaking also, feel free to do that whenever and we'll follow-up with an update to the node package

sounds good. You will have to email us from your registered email ID though.

<@498057949541826571> It looks like there's an issue upgrading supertokens-node:
- Authenticating to the prod dashboard is still working
- Authenticating to a dev-mode dashboard is still working (using `supertokens-node@13.1.2`)
- Authenticating to a dev-mode dashboard in a preview app is not working (using `supertokens-node@13.4.2`)

When you say not working, what are you observing?

Ah, yeah that's a key detail 🙃 

- Request is `POST /api/auth/dashboard/api/key/validate`
- This includes a `Bearer API_KEY` header as expected
- 401 response with `{"message":"Unauthorised access"}` as the body

have you done dashboard.init in the recipe list with an API key?

or do you use email password login to access the dashboard?

The former – I'd be interested in email/password though as it seems easier to manage security

i think if you remove the api key part, and just do dashboard.init on the backend, it will show you the email password login UI

as to why the api key method stopped working, <@292333473786494976> can help when he is available.

In case it's useful, I'll include examples of successful and failed requests:

successful

failed

Thanks. Will wait for <@292333473786494976> to help. Did the email password method work though?

Hey <@730001960308310048> 

There was a bug with the API key based login in the Node SDK that would result in this behaviour. It was fixed in 14.0.1, if you do want to use an API key for the dashboard you'll have to upgrade

Hey <@292333473786494976> thanks for the heads-up! We're happy with email/password for now.

Confirming that we now have search on the dashboard, thanks everyone