How to do automatic signup for first-time-login-users via social login in Auth0

[anoopdecodes]

I followed the quickstart tutorial from Auth0 website and successfully implemented a login feature for my website, using a test account which was added as a test user in auth0 dashboard. I’m using only the social login options; facebook and google, the username-password-sign-in option is disabled.
I want to to signup all users who login my website using their social login. Also I want to use the user metadata option to store user data. Right now, when I try to login using a new account, after the Auth0 Lock screen, I get the permissions screens “auth0.com wants to access your Google Account” and I click allow, then I get Authorize App
consent popup with message “myapp is requesting access to your myappsignin tenant”. I want disable the consent and automatically add users to auth0 user metadata. How do i do that in auth0?

I found this and this while searching for an answer. Anybody please help me understand.

[James.Morrison]

Hello there @anoopdecodes and first let me start off with apologize for the delay in response!

Now to focus on your question I believe the best response was one you linked but I’ll quote below for others:

@jmangelo

The creation/registration of a social user depends on an external identity provider and it’s a process that will most likely require end-user interaction. Having said that, if you create your own custom social OAuth2 connection pointing to an OAuth2 mock API that does not require any sort of end-user interaction ( this is dangerous, read the full answer for caveats ) then you may be able to achieve what you want.

The sequence of steps would be something like:

1. Create a custom OAuth2 connection named CUSTOM .
2. Perform a request to the /authorize endpoint that includes a connection parameter with a value of CUSTOM .
3. The custom OAuth2 connection was implemented in a way that the requests for authentication are automatically satisfied with test user information.

The above would mean you could trigger authentication/registration of a social test user (one where isSocial is true since it’s coming from a custom OAuth2 connection) with just a GET request that would not require any sort of manual interaction. Have in mind that something like this should only be done in a test account, because that custom OAuth2 connection would basically allow access as a test user to anyone.

So in reviewing this suggestion, it’s really important to look at the danger assoicated with it. Is there a particular reason why feel disabling the consent messaging is ideal? I would love to share a more in-depth conversation about this together if you are still facing this challenge.

Due to the age of this question I will keep the topic open for 10 days unless I hear otherwise from you. Please let me know if there is any way I can assist.