And if possible to have a “drop in replacement using OAuth” for what we have today, is there an arch...
n
And if possible to have a “drop in replacement using OAuth” for what we have today, is there an architecture where: The user hits login -> redirect to a service that’s using SuperTokens+Jackson under the hood, they login, we issue an Access Token, RT/Cookie, and issue it to my front end? And then on the backend I can point it at a JWKS for a token verification?
r
Hey @nicolasfry
Supertokens is not yet an OAuth provider. Therefore auth integrations with zapier won’t work. We are working on adding the OAuth provider feature and it should be out in a few months.
So for now, users sign in on the frontend and get back session tokens (access and refresh tokens) as cookies. This works well for cases that dont require OAuth (which is most websites / apps)
n
Thanks @rp_st, can I be added to a list (or is there an issue) to see when this is available? I’m about to hit the upper end on my auth0 self service plan due to oidc/SAML enterprise connections and get wacked with a big bill. Trying to not rip and replace twice
r
once it closes, it means we have released it, or will release that week
3 Views