Welcome & Hello Ambassadors. 🙌

Hello all, Vanshika here ! Thanks for the invite @User 🙌

Hi all, Puru here. Thanks to @User Tyagi for inviting me to the Ambassador program 🙇‍♂️

@User could you please ping @rp to get started with GitHub contributions

@User , there is a contributing channel here. You can post your message there.

I am trying to translate some parts of form but i find it hard to do so.I am trying to translate "or" divider and "continue with facebook" label.Is this possible with build in components?

You could run JS in a useEffect, find those elements using DOM functions and change the text

We don’t have translatable components yet. But will probably work on it soonish.. until then, the above recommendation is the best way.

Thanks for the solution

Are websockets supposed to work on a golang backend when wrapped with the supertokens verification wrapper?

Seems the DoneWriter doesn't implement Hijack which is required to upgrade a connection to a websocket

I don't think websockets will work with the verification wrapper function. Haven't tried that yet.

If you want, you can make an issue about this on our github and we can check it out sometime in the coming days.

or even raise a PR to add support for this?

As a work around, you can enable the JWT feature, and use a JWT for auth in websockets.

my usecase is basically to use supertokens for a bunch of API requests, and also to authenticate a proxied websocket, so basically I'm just using supertokens to authenticate the connection and then proxy the entire websocket connection to another server (with some additional injected authentication headers)

It's a bit of a weird usecase

hmm. I'm not sure I quite understand what "authenticate a proxied websocket" means - What is proxied websockets? Is the socket connection from the frontend to the backend? Or from backend to backend?

So basically 1. Browser initiates connection with API server using supertokens cookies 2. API server validates supertokens cookies and opens websocket connection with backend server with an authorization header 3. backend server validates authorization header and starts streaming data to the API server 4. API server proxies all data between the backend server and browser

Ahh i see.

The key thing that makes this kinda hard is the backend server isn't "trusted" and so it will have no access to literally anything.

So the issue is coming in step (2)? Where you are unable to open a socket connection to the backend server?

No that part works fine

The part that doesn't work is the responsewriter that supertokens returns is incapable of hijacking the connection

so it can't upgrade the connection between the browser and the API server to a websocket

I'm pretty sure it's because supertokens is wrapping the responsewriter like this

Oooooo! I see.

What do you suggest?

implementing http.Hijack would totally solve the problem