Hi, I was wondering is it possible to implement Microsoft / Outlook SSO with supertoken? And if yes, where can I find some resources about that?

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?

When I access the application in firefox, I get an error "Please provide a valid domain name" in the frontendConfig section.

hey guys, my auth is going very slow in prod - i think my instance needs to be restarted. Anyway someone can help me with this asap?

Hi guys, the instructions for the docs aren't working on my Macbook M1. Following this: https://supertokens.com/docs/community/versioning I get this error :

ℹ Starting the development server...
Docusaurus website is running at "http://localhost:3000/".
Browserslist: caniuse-lite is outdated. Please run:
npx browserslist@latest --update-db

Why you should do it regularly:
https://github.com/browserslist/browserslist#browsers-data-updating

● Client █████████████████████████ building (10%) 0/5 entries 1/5 dependencies 0/0 modules 0 ac
tive 
 

ℹ ｢wds｣: Project is running at http://0.0.0.0:3000/
ℹ ｢wds｣: webpack output is served from /
ℹ ｢wds｣: Content not from webpack is served from /Users/rs/Documents/Development/docs/v2
ℹ ｢wds｣: 404s will fallback to /index.html
node:internal/crypto/hash:71
  this[kHandle] = new _Hash(algorithm, xofLen);
                  ^

Error: error:0308010C:digital envelope routines::unsupported
    at new Hash (node:internal/crypto/hash:71:19)
    at Object.createHash (node:crypto:133:10)

I ran:

git clone https://github.com/supertokens/docs.git

git checkout 0.9.0

and then

cd v2

and then

npm i -d

and then when trying to run I got the error. Just to let you know 🙂

it is possible with the frontend SDK (the web-js one) to fetch user metadata?

Is it possible to change the header where the authorization bearer is placed? E.g. use st-authorization instead of authorization

The issue I am having is how to check if the user is logged in and show them another navbar instead of the navbar for everyone who is not logged in. I am using supertokens to verify my users, this is my app.tsx. This is my code -

import { SuperTokensConfig, PreBuiltUIList } from './database/auth/supertoken';
import SuperTokens, { SuperTokensWrapper } from "supertokens-auth-react";
import { Routes, BrowserRouter as Router, Route } from "react-router-dom";
import { getSuperTokensRoutesForReactRouterDom } from 'supertokens-auth-react/ui'
import { SessionAuth, SessionContext } from "supertokens-auth-react/recipe/session"

//Components
import Navbar from './components/nav/Navbar';
import NavbarAuth from './components/nav/NavbarAuth';
//Free Routes
import Home from './routes/free/Home';
//Protected User Routes
import Profile from './routes/user/Profile';
//Protecte Admin Routes


SuperTokens.init(SuperTokensConfig);

function App() {
  //Here
  const check = SessionContext;
  return (
<SuperTokensWrapper>
  <div className='App app-container'>
    <Router>
      {check ? <Navbar /> : <NavbarAuth />}

      <Routes>
        {/* This shows the login UI on "/auth" route */}
        {getSuperTokensRoutesForReactRouterDom(require("react-router-dom"), PreBuiltUIList)}

        {/* Unprotected route */}
        <Route path="/" element={<Home />} />
        {/* Unprotected route */}

        {/* Protected route Users */}
        <Route
          path="/profile" element={
            /* This protects the "/" route so that it shows
          <Home /> only if the user is logged in.
          Else it redirects the user to "/auth" */
            <SessionAuth>
              <Profile />
            </SessionAuth>
          } />
        {/* Protected route Users */}

      </Routes>
    </Router>
  </div>
</SuperTokensWrapper>
  );
}

export default App;

Hey, @rp_st I have integrated supertokens passwordless receipe in backend python(fastAPI) where I used 2 endpoints /signinup/code and /signinup/code/consume It's working fine and override these both endpoints and added some logic, so our frontend react-native have to use backend API only but if we are using backend API we get session false when we are using supertokens endpoint for the same then everything is working good FE can get session True Thanks!!

is there any to log out the user if user is idle for 10 mins without?