lack of bandwidth at the moment. We will be working on golang in the coming weeks for sure to get it up to date with the latest version of the core.

"weeks" is a great timeframe haha I'm still doing demos with no authN/authZ at all here so the bar is quite low, but you know how it is... you want to choose techs that are straightforward early but won't be limiting later on

yea makes sense.. that's our aim. In short: - You can customise the UI / UX on the frontend to whatever you'd like (on your own domain) - You will be able to override any of the auth APIs we expose via the go SDK. - If self hosting, you control all the data, and can change our db schema or use your own schema and write wrappers that will read / write to your schema - It's all open source, so you can even fork everything and modify any part as per your needs if something is limiting in the future (worst case).

Is Discord a possibility for Third Party Providers?

@User yup! As long as Discord follows the standard OAuth 2.0 protocol (which they seem to).

You can create an issue about it on our github, and we can make it.

Ok, cool! Thanks

Seems like it already exists so Im not going to make a new issue https://github.com/supertokens/supertokens-node/issues/88

👍

taking technical questions back to public channels

I thought I found some community-contributed k8s manifests for deploying the db and the core service, but I can't seem to find them now-- did I imagine that or maybe confuse the memory with some other package?

oh... well that's awkward, I was remembering FusionAuth's community stuff uhm... perhaps after I get this working there's some place I could share it?

> did I imagine that or maybe confuse the memory with some other package? Probably... > perhaps after I get this working there's some place I could share it? Yea. Can create a PR on our docker image repos? - https://github.com/supertokens/supertokens-docker-mysql - https://github.com/supertokens/supertokens-docker-postgresql - https://github.com/supertokens/supertokens-docker-mongodb

Hello! New to Supertokens. Just heard of it from reddit. I have a couple questions: 1. Does supertokens Sessions provide just an API for login and logout? Like how Firebase Auth does? I'd ideally want a solution where I could just use a function like

supertokensInstance.signInWithEmailAndPassword()

. 2. Why is SuperTokens for React different from the Plain JS package? AFAIK they provide the same functionality. Unless the React package auto-generates views (

/auth/login

)... Supertokens looks really exciting. Looking forward to using it!

> Does supertokens Sessions provide just an API for login and logout? Like how Firebase Auth does? I'd ideally want a solution where I could just use a function like supertokensInstance.signInWithEmailAndPassword(). For this, please follow our emailpassword recipe. You will get a UI on the frontend + APIs exposed on the backend + httpOnly cookies session management with a few lines of code. See https://supertokens.io/docs/emailpassword/introduction > Why is SuperTokens for React different from the Plain JS package? AFAIK they provide the same functionality. Unless the React package auto-generates views (/auth/login)... There are two frontend libs: - supertokens-website: This is a plain JS lib that is used only for session management. - supertokens-auth-react: This is a react specific lib that renders React login components on your website. It also does session management (by using supertokens-website.

1) Oh, alright. Thanks! 2) So it's just the react rendering which is the difference?

> So it's just the react rendering which is the difference? React rendering of login widgets, and handling their API calls etc.. + routing across auth related pages, and providing a session wrapper that protect pages that require auth (else redirect users to login page).

Alright. Can I use all this functionality; session wrapper, etc, etc in the Plain JS Package?

unfortunately, not yet 😦

We are working on a vanilla JS package though. Just not sure about its timeline.. parhaps a month or two.

Oh.

Sounds great.

Yeah I had the same question too. Is it possible to do this right now via http requests? I am talking about doing the signin, signup all through http requests if its not available on the plain js package

Yes. It is. The API spec exposed by the Sdk can be found here: https://github.com/supertokens/frontend-driver-interface/blob/master/v1.8.0.md (See which the APIs specific to your recipe)

and for sessions, you can still use supertokens-website package - which is vanilla JS. So you can ignore the API spec for that recipe.

Awesome, so in reality the frontend driver interface includes everything

But the backend was the one that is behind all the features

So for frontend, only the react SDK includes all the UI components and the ability for querying the backend.

And on the backend, only the node SDK has all those APIs mentioned in the spec link above

But we are working on supporting more tech stacks.