And I wrap the protected page component with it. And that makes Typescript complain, about it not having the requiredAuth prop

Yup.. So you can use it like this:

<ThirdPartyEmailPasswordAuthNoSSR requireAuth={false}>
  <YourComponent />
</ThirdPartyEmailPasswordAuthNoSSR>

About the TS complaint, for now, you can do something like this (as a hack.. until we fix it):

<ThirdPartyEmailPasswordAuthNoSSR {...{requireAuth: false} as any}}>
  <YourComponent />
</ThirdPartyEmailPasswordAuthNoSSR>

Great! It works. Thanks, you've been a great help. Take care.

If you want, you can create an issue about the TS error on out github.

@User , I have created an issue for this on our github: https://github.com/supertokens/docs/issues/23 Feel free to watch it so that when it's fixed, you can be notified 🙂

Just playing a bit around with SuperTokens.io. Following the documentation: https://supertokens.github.io/supertokens-node-mongo-ref-jwt/docs/backend/installation - I get error: npm i --save supertokens-node-mongo-ref-jwt@^3.3.0 npm ERR! code ETARGET npm ERR! notarget No matching version found for supertokens-node-mongo-ref-jwt@^3.3.0.

Ah, I just saw it's based on Java, after plyaing around with the getting started tutorials. That kinda kills it for me

However, looking at https://supertokens.github.io/supertokens-node-mongo-ref-jwt/docs/introduction/what-and-why it doesn't say anything about Java. I am super confused.

hey @User , apologies for this confusion.. https://supertokens.github.io/supertokens-node-mongo-ref-jwt/docs/backend/installation docs are old and deprecated.. You want to follow this: https://supertokens.io/docs/community/introduction

Also, we support node and react at the moment. The Java part is just the http service which forms a part of the whole solution (you don't need to use / code in Java)

I see. Thanks rp

Is there a way to set it up to use a custom email server?

Cause I'd like it to use my own domain

@User yes. You can. - For email verification emails: https://supertokens.io/recipe-redirect?to=/common-customizations/email-verification/email-verification-email&hide=session - For reset password emails: https://supertokens.io/recipe-redirect?to=/common-customizations/reset-password/password-reset-email&hide=session,thirdparty

Does Supertoken support a work email based social login. For example, is it possible to use supertoken to support identities through Google suite & Office 365 ONLY?

@User yes. You will want to do the following: - Use sign in with the relevant social providers you want to use (google and outlook?) - since we don't have outlook at the moment, you can add that as a custom provider (see https://supertokens.io/docs/thirdpartyemailpassword/common-customizations/signup-form/custom-providers) - Then override the signinup API in the NodeSDK to reject emails that do not meet a specific criteria of yours - If you wait for a few days, we will release a new version of our node SDK which will make this operation very simple.

Thanks for the response @User. We can wait for the NodeSDK to be updated - do yo uhave an approximate ETA on when this can be expected?

2-3 days from now

@User Additionally, where can I find the documentation of creating a custom provider (in our case it will be Google suite & Office 365) .ts files?

@User ^

@User I went thru the documentation but did not find any additional documentation on writing a custom connector. Perhaps additional documentation wil lhelp

So you want to connection to google suite via sign in with google right?

And office 365 would be sign in with outlook (which would take the user to outlook.com)?

Yes, we want identity confirmation for google workspace customer (not free gmail users). Similarly, Microsoft Office 365 has a cloud identity (not their free outlook.com email). Both these are needed for confirming users are using their work emails for signup..

Yes. So the way it would work is: - You use our sign in with google provider - You need to implement custom sign in with outlook provider (the link i shared previously shows you how to add a custom third party provider using our node SDK) - Post our new release (2-3 days from now), you would need to override the sign up / in API in the backend to add a check for the email being used - if it's @gmail.com or @outlook.com / @hotmail.com, then return an error that is showed on the frontend to the user. All the above can be done within a span on a few hours..

The link I had shared above provides info about how you can add a custom social provider (you could even create a PR for our repo for this).

@User It is more complicated than removing the free email domains offered by Office 365 and Google suite. For example, see the documentation from Okta about O365 SSO integration (https://www.okta.com/integrations/microsoft-office-365/#capabilities) and from their recently acquired, Auth0 (https://auth0.com/docs/integrations/sso/office-365)

Perhaps I may have misunderstood your requirement then.. it would be best to discuss this over a call.. I have DM'd you my contact info 🙂

@User I have dropped you a DM on the call