Oh, what browser are you using?

Chrome, but it’s been acting up all day so maybe I just need to reinstall it

Even with plugins all disabled

Ah fair

Ok, I see it now. Thanks @User. I do have a follow up question though on if this works with Expo? Currently we’re using Expo for roughing things out since it seems to simplify some things.

It should!

The SDK we have only helps with session management at the moment. For login, you will have to build your own UI and call the APIs exposed by our backend SDK using axios / fetch yourself

does supertokens allow me to integrate with a customer's own IdP via SAML?

and if so do i have to write code to make it happen for each customer?

Hey! We don’t have a native SAML integration, but you can use us and another service like https://ossoapp.com/ to get SAML. They even have a supertokens specific integration guide here: https://ossoapp.com/docs/consume/supertokens

thank you!

Hello everyone, trying to understand if the ST would work for our multi-domain setup and would appreciate your feedback. We have multiple sites e.g.: abc.com xyz.com I'd like to use ST as a third-party login service so that both sites integrate it, and once you login into abc.com we set the first-party cookie using our login service let's say auth.mycompany.com , you visit xyz.com - we see the cookie and log you in automatically

Hey @stany your setup requires that supertokens be an OAuth 2.0 provider. Which we are not at the moment. That’s the only missing piece here unfortunately.

That being said, you can still use us if you can figure out how to use another solution that provides OAuth along side supertokens.

Got it, thanks for a quick response, currently investigating custom oidc + cognito to solve this, but found you guys and thought would be awesome to try to avoid all the configuration burden for the solution specified.

Fair! 🙌

Hi! Somehow my authentication is not renewed although I'm using the fastify middleware. I understood there was nothing to do on the client-side either so I'm a bit at a loss as to how to debug/fix this. Does anyone have a clue?

when you say renewed, you mean the session being refreshed?

If yes, is the refresh API being called at all by the frontend?

indeed I meant refresh No, my frontend does not expressly call the refresh API

hmm. So the supertokens.init is called on the frontend on app start, correct?

yes

And do you have your own custom fetch interceptors?

I did not set any custom interceptor and we don't use axios just regular fetch

alright! Do the regular API calls to your application's APIs (that do succeed) have a header like

rid: "anti-csrf"

in them?

I'm checking that

we use helmet so maybe it is set by that middleware

hmm. If the fetch interceptor provided by us is getting applied as expected, all requests to your app's APIs should have

rid: "anti-csrf"

in it.

If they don't then we know that the interceptor is not being applied - which then wouldn't call refresh either.

ok I'll log that header see what I get