hi, @rp_st We encountered this error when we tried to log in. But we did not make any changes to supertokens that would affect this. why could this be? SuperTokens core threw an error for a request to path: '/public/recipe/signin' with status code: 403 and message: Email password login not enabled for tenant.

Hey 👋 I'm trying to authenticate via Google using the ThirdParty recipe. We're using NextJS only for the frontend, NestJS for the API, and self-hosted SuperTokens core. The

authorisationUrlGET

request runs successfully but the

signInUpPOST

request receives a 500 in the frontend, and a 401 in the backend. The backend error message is just "Request failed with status code 401". We've successfully used the passwordless recipe with this setup so unsure why Google OAuth is not working. Any ideas?

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;

Having issues with using selfhosted with SSL and Docker @rp_st

Do you need a

core

to use supertokens with

nextjs

?

Hi, there. I'm trying to implement Sign In with Google using the following instruction https://supertokens.com/docs/thirdpartyemailpassword/custom-ui/thirdparty-login. But when I call

thirdPartySignInAndUp

after redirect it throws me error `Error: No instance of ThirdPartyEmailPassword found. Make sure to call the ThirdPartyEmailPassword.init method. `But, actually, it was successfully initialised as I was able to call getAuthorisationURLWithQueryParamsAndSetState to generate auth url. Any ideas what I'm doing wrong?

Is there a management background for ordinary users, such as users can change passwords, modify email？

Auth Redirection - is there a version of this that I can use for supertokens-web-js? Also have the same question for setting

useShadowDom: false

import SuperTokens from "supertokens-auth-react";
import ThirdPartyEmailPassword from "supertokens-auth-react/recipe/thirdpartyemailpassword";

SuperTokens.init({
    appInfo: {
        apiDomain: "...",
        appName: "...",
        websiteDomain: "...",
    },
    recipeList: [
        ThirdPartyEmailPassword.init({
            getRedirectionURL: async (context) => {
                if (context.action === "SUCCESS") {
                    if (context.redirectToPath !== undefined) {
                        // we are navigating back to where the user was before they authenticated
                        return context.redirectToPath;
                    }
                    return "/dashboard";
                }
                return undefined;
            }
        }),
    ]
});

@rp_st I'm trying to get a user by the metadata value. For example, my users have a metadata field "stripe_customer_id" and I want to get a user by this value. I'm using ThirdPartyEmailPassword recipe but I can only see

getUserById

and

getUsersByEmail

Hello. Is https://artifacthub.io/packages/helm/graphql-hive-subcharts/supertokens your official Helm repository for Supertokens Core?