with your code.

its a little different as it doesn't use JWTs Redis for access token storage and MySql for auth token/refresh token storage

hmm. i'll have a look and then decide how it fits into our solution. If it's quite different, then you can open source it under your account if you want.

okay

anyways, here is the supertokens-go github link: https://github.com/supertokens/supertokens-go

feel free to fork and then issue a pull request.

i can always write a one to one port for go if you would like

i prefer that happens with our newest implementation. will let u know! thanks.

(which is not yet released on github)

ok

!d bump

!d bump

!d bump

!d bump

if the cookies are set to be unsecure

should sAccessToken and sRefreshTokne come in in the cookies without an HttpOnly flag

No. They should come with secure flag as false. HttpOnly is still true

ok

@tredstone I recommend to keep the cookies secure to false only for development mode. For production, you should have an SSL certificate and make cookies secure. You can get a free SSL certificate using letsencrypt.org (so I have heard)

will do. I managed to sort out my problem earlier. I've also heard of certbot for SSL cert management as well

Oh. I haven’t heard of that. But will check it out

I have an idea i want to work on but im really afraid of using the wrong stack

What languages do u already know?

Python javascript

but wont mind learning something new to try to be the latest best

I see. Is ur application something that will have a lot of database calls in each API call? Or a lot of computation like matrix multiplications