Use social auth google settings to restrict domain instead of custom code.

[gkapoor121212]

Currently, the users which login into system require an Axelerant Gmail ID and this condition has been added via the custom code in the ct_users module. We can remove the custom code and use configurations provided by the Social auth google module or google developer app settings.

[hussainweb]

Last I checked, Social Auth Google didn't have such options. We considered writing a module but it seemed too trivial and I just wrote the custom code. It's worth reconsidering all the options again.

[hussainweb]

We can't remove the code in ct_user yet as it is responsible for activating the user. Social Auth module has no feature to enable users created through Social Auth flow. It follows the Drupal configuration for new accounts and we can't remove admin verification for that as /user/register callback is still enabled.

[gkapoor121212]

@hussainweb This is the line of code that I thought should be changed if (preg_match('/.*@axelerant\\.com$/i', $user_email) > 0) { as it is restricting login to only users with Axelerant ID. If that's not the case we can keep this issue closed.

[hussainweb]

Ah, your point is to make this generic and usable by orgs other than Axelerant?

[gkapoor121212]

@hussainweb Yes.

[hussainweb]

Understood, @gkapoor121212. I created #33 to handle this.