• ravibaskaran

    ravibaskaran

    1 year ago
    @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?
  • r

    rp

    1 year ago
    @User ^
  • ravibaskaran

    ravibaskaran

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

    rp

    1 year ago
    So you want to connection to google suite via sign in with google right?
  • r

    rp

    1 year ago
    And office 365 would be sign in with outlook (which would take the user to outlook.com)?
  • ravibaskaran

    ravibaskaran

    1 year ago
    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..
  • r

    rp

    1 year ago
    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..
  • r

    rp

    1 year ago
    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).
  • ravibaskaran

    ravibaskaran

    1 year ago
    @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)