Just to be more clear - we are looking at the activation aspect of the user - not the registering. The plugin works fine to register the user - but we require them to be registered even if the site requires them to also be activated. So the plugin is functioning properly but isn't catering for the activation requirement - which seems to be the problem. We are looking into a solution to override the activation requirement for social login.
Some more info from the rainlab.user plugin:
Activation is a process of vetting a user who joins the site. By default, users are activated automatically when they register and an activated account is required to sign in.
The Activation mode specifies the activation workflow:
Automatic: This mode will automatically activate a user when they first register. This is the same as disabling activation entirely and is the default setting.
User: The user can activate their account by responding to a confirmation message sent to their nominated email address.
Administrator: The user can only be activated by an administrator via the back-end area.
You can allow users to sign in without activating by switching Sign in requires activation to the OFF setting. This is useful for minimising friction when registering, however with this approach it is often a good idea to disable any "identity sensitive" features until the user has been activated, such as posting content. Alternatively, you could implement a grace period that deletes users (with sufficient warning!) who have not activated within a given period of time.
Users have the ability to resend the activation email by clicking Send the verification email again found in the Account component.