Topics created by maximiliano.riffo

@maximiliano-riffo,

Based on the documentation, it does seem that a differentiation can be drawn out, but manually only (see bold below).

Complete the google login API - Doc

(https://fusionauth.io/docs/v1/tech/apis/identity-providers/google/#complete-the-google-login )

The user does not need to exist yet in FusionAuth to utilize this API. The token returned from Google will be used to retrieve the user’s email address, if that user does not yet exist in FusionAuth the user will be created. If create registration has been enabled for this identity provider and the user does not yet have a registration for this application, a registration will be automatically created for the user. The user will be assigned any default roles configured for the application. If create registration has not been enabled, a registration will not be created if one does not yet exist. This last scenario is useful if you wish to manually provision users and then subsequently allow them to login with Google.

So it would seem, without testing this myself, if you disabled create self service registration in your application, and got the 202 code, that might be your cue to hit a registration endpoint to register that user?

registrations.png

Another option may be to enlist the help of a webhook and/or event to watch the registrations and take action based on that.

https://fusionauth.io/docs/v1/tech/events-webhooks/

Let me know if I am understanding correctly or if there is any other clarifying information.

Thanks!
Josh

@maximiliano-riffo , welcome to the FusionAuth community!

I don't understand what you are trying to do. Are you trying to verify a user's email without sending them an email? I'm not sure I understand how that would work.

If you want to build your own verification system, you can do that.

Create an attribute user.data.verifiedBySMS on user creation and set it to false. Send the user an SMS using any SMS provider. Include the code and a link to a page in your app. When the user enters the code in the app, update user.data.verifiedBySMS to true. Build your application UI to test the value of user.data.verifiedBySMS. You could also put it in a JWT.

Maybe I misunderstand your question, though.