Hi, I just wanted to know about how we can integrate supertokens with SAML. For eg. We are providing Google provider for third party auth. So if we want to provide our app as a custom application in Google workspace SSO. How will I be able to configure it with supertokens third party auth. Even if I get a minimum information from your side , it would be really helpful.

how can I check authentication in swagger? because we are using cookies-based authentication.

Hi. I have a problem while doing fetch from the front end to my backend I get 401 non-authorize. In docs, it said that if 8using fetch no actions are needed, what I'm missng

Is there a way to fix this error message. It seems like a css property which got set in the library itself

I tried setting some data using merge access token payload on the backend and then useSessionContxt to get the payload on the frontend. I am able to set the data properly on the backend but when I try to get it on the frontend it is always an empty object {}. Any idea why?

Hi, How can i prevent the input field from changing its background on focus? (React) I have set the following styles in ThirdPartyEmailPassword:

inputWrapper: {
  backgroundColor: 'var(--input-background)',
  borderColor: 'var(--input-border)'
},
input: {
  color: 'var(--text-color)',
}

Hello everyone, I have a react frontend react app that consumes a backend api written in Ruby on Rails. I would love to use SuperTokens for authentication but I'm afraid that it won't work because SuperTokens doesn't support Ruby as backend yet. Would there still be a possibility for it working if I just implement it in the frontend with the react library? I was thinking maybe it would work if I just save the matching user record of the logged in user in the backend database and compare it.

Hi, you described that using your access token is more secure than JWT. But on your site not so many reasons why and its a problem. So can you write a bit more detailed comparison between your access token and JWT?

I noticed that the Auth0 external id (

sub

) for the google provider was

google-oauth2|<ID>

. Now with supertokens I am building this within

createNewSession

, for mapping the accounts.

const externalUserId = user.thirdParty ? `${user.thirdParty.id}|${user.thirdParty.userId}` : null;

I noticed that

user.thirdParty.id

, here is

google

and not

google-oauth2

. Is it safe for me to simply replace the

google|

part with

google-oauth2

, is the

<ID>

part of the auth0 sub stable?

Can a SuperToken dev take a look at this and let me know which is the best way to "connect provider" with XenForo and SuperTokens https://xenforo.com/community/resources/th-connected-account-providers.8488/