Maybe something hre? https://github.com/react-hook-form/devtools/blob/master/package.json

It's using

"@emotion/core": "^10.0.28",
    "@emotion/styled": "^10.0.27",

at some point i anticipate that we will want to run the supertokens core container on a VM by itself in this case, what is the best way to do this securely? one idea i had was using an nginxa reverse proxy (listening on port 443), and running instances of the Supertokens Core with API_KEYs enabled (on the same VM) Is this correct?

@User hmmmm. Will have a look at the emotion issue. Thanks!

Yep sure thing.

@tredstone yea.. that’s an excellent approach. The nginx can provide an Https connection and have a http reverse proxy to the SuperTokens-core which uses some API KEY that you specify.

signing keys are all completely managed by the supertokens core?

Yes

the details of the singing keys posted anywhere? like type and bit length?

i was looking at this: https://supertokens.io/blog/the-best-way-to-securely-manage-user-sessions

Not yet. But you can inspect the code for it, and have a look at the signing key in the key_value table yourself

Here is the function that creates the signing key https://github.com/supertokens/supertokens-core/blob/master/src/main/java/io/supertokens/utils/Utils.java

public static String generateNewSigningKey()

Oops.. not that function.

The JWT signing method is Rsa which uses a public private key. The private key is used for signing and public key for verifying. The function. That creates the 2 keys is here

thank you

@User can you please enable Dev tools and see if there is an error in the browser console? That may help us debug the issue better

There was none when I checked

Hmm I see. Thanks!

Hey @User , this seems to be related with the issue that someone else had earlier this week. When two different packages uses emotion there are css clashes. This branch (not released yet) should fix your issue (hopefully) https://github.com/supertokens/supertokens-auth-react/tree/0.3. If you temporarily change your `package.json `entry from

"supertokens-auth-react: "^0.2.2"

to

"supertokens-auth-react": "supertokens/supertokens-auth-react#0.3"

and run

rm -rf ./node_modules/supertokens-auth-react && npm cache clean --force && npm install

that should work . Let me know if that fixed for you or else I'll have to investigate a bit more.

Another thing you could try is to disable shadow Dom to see if it has any effect on your styling. See https://supertokens.io/docs/emailpassword/common-customizations/signin-form/password-managers

Thanks!

I’ll try this tomorrow

I'm having trouble with the

signOut

function. It only seems to work when I clear my cookies. Do I then need to programmatically clear cookies everytime a user signs out? @User

No u don’t

Please make sure your apiDomian on the backend is correctly set

Backend and frontend*

And also that your websiteDomain is correctly set too