Im not sure

@rs, you can use SAML with us by integrating with ossoapp.com and using that as a third party provider with SuperTokens. Native SAML support from our end is gonna be a while (probably sometime next year)

@User , Change your init to:

go
errr := supertokens.Init(supertokens.TypeInput{
        Supertokens: &supertokens.ConnectionInfo{
            // These are the connection details of the app you created on supertokens.io
            ConnectionURI: "http://localhost:3567/",
            APIKey:        "",
        },
        AppInfo: supertokens.AppInfo{
            AppName:       "GOInfluencer",
            APIDomain:     "http://localhost:8080/",
            WebsiteDomain: "http://localhost:8081/",
        },
        RecipeList: []supertokens.Recipe{
            emailpassword.Init(&epmodels.TypeInput{
                ResetPasswordUsingTokenFeature: &epmodels.TypeInputResetPasswordUsingTokenFeature{CreateAndSendCustomEmail: func(user epmodels.User, passwordResetURLWithToken string) {
                    fmt.Println(passwordResetURLWithToken)
                }},
            }),
            session.Init(nil),
        },
    })

    if errr != nil {
        panic(errr.Error())
    }

And when you call the API, see if you the URL is printed or not.

okay

No just status OK

hmm.. strange. Let me debug

okay thank you

Strange.. it is printing out the URL for me with a very similar config

oh

This is my go file:

go
package main

import (
    "fmt"
    "net/http"

    "github.com/go-chi/chi/v5"
    "github.com/go-chi/cors"
    "github.com/supertokens/supertokens-golang/recipe/emailpassword"
    "github.com/supertokens/supertokens-golang/recipe/emailpassword/epmodels"
    "github.com/supertokens/supertokens-golang/recipe/session"
    "github.com/supertokens/supertokens-golang/supertokens"
)

func main() {
    err := supertokens.Init(supertokens.TypeInput{
        Supertokens: &supertokens.ConnectionInfo{
            ConnectionURI: "https://try.supertokens.io",
        },
        AppInfo: supertokens.AppInfo{
            AppName:       "SuperTokens Demo App",
            APIDomain:     "http://localhost:3001",
            WebsiteDomain: "http://localhost:3000",
        },
        RecipeList: []supertokens.Recipe{
            emailpassword.Init(&epmodels.TypeInput{
                ResetPasswordUsingTokenFeature: &epmodels.TypeInputResetPasswordUsingTokenFeature{CreateAndSendCustomEmail: func(user epmodels.User, passwordResetURLWithToken string) {
                    fmt.Println(passwordResetURLWithToken)
                }},
            }),
            session.Init(nil),
        },
    })

    if err != nil {
        panic(err.Error())
    }

    r := chi.NewRouter()

    r.Use(cors.Handler(cors.Options{
        AllowedOrigins:   []string{"http://localhost:3000"},
        AllowedMethods:   []string{"GET", "POST", "PUT", "DELETE", "OPTIONS"},
        AllowedHeaders:   append([]string{"Content-Type"}, supertokens.GetAllCORSHeaders()...),
        AllowCredentials: true,
    }))

    r.Use(supertokens.Middleware)

    http.ListenAndServe(":3001", r)
}

And I get

http://localhost:3000/auth/reset-password?token=YmNlYjgyNjkzY2VhZDRjZGQzMTcyNjlmMWM2YzU5NzIzZTRk....0ZWMwMmUz&rid=emailpassword

as the output on the console

Does it have something to do with my connection uri?

Shouldn't be.

Can you remove the middleware and then query - you should get a 404. Can you confirm that?

okay

404 page not found

alright! So the only explanation is that the email you are using to query the API doesn't actually exist in the core

what's the user you created in the core?

arihantverma52@gmail.com

when im trying to sign up again with the same email it says that user already exists

hmm. Free for a quick call?

yes sure

meet.google.com/ehq-hxxu-ono

Hey, in multi tenancy, when can we expect any example implementation for golang or some kind of documentation?

So we have partial support for multi tenancy. Can you describe your requirement a bit please?

Basically our app deals with two personas (Brands & Users). From backend perspective we are building a single service (& database) to handle the auth while the clients would be separate. We want to propagate and store this tenant information in db.

A few questions: - Would you want to allow the same email to be used by someone for Brands and Users? Or is it OK if the email is unique across those two types of users? - If the frontend domain for both of them different? If yes, how is it different (different sub domains or different top level domains as well)? - If the domains for both are different, would the login for each of them be on their respective site or a common login form?

Hi @User Let me answer these questions. - Yes, the same email should have different identities when signed up as a brand and user. - Different subdomains - Login on client side would be different on their respected subdomains

> Yes, the same email should have different identities when signed up as a brand and user. Okay. So we don't have different user pools at the moment, but what you can do is to override the backend functions (signUp, signIn, etc) to modify the input email in the following way (see this section: https://supertokens.io/docs/emailpassword/advanced-customizations/backend-functions-override/about): - If it's a brand user signing in / up, then change their email to add a

+brand

to it. So user@example.com would become user+brand@example.com - If it's a normal user signing in / up, then change their email to add a

+user

to it, similarly to the above point. This way, even if these users are all in the same user pool, a person can use the same email for both a brand and a user. This does not actually affect sending emails to them. > Different subdomains & Login on client side would be different on their respected subdomains Alright. Follow up questions: - Are you using our supertokens-auth-react package on the frontend or supertokens-website? - After logging in, would those users be redirected to a different sub domain or stay within their own sub domain?