Handle Google login primary domain changes

[markspolakovs]

Handle Google login primary domain changes

[linear]

OLN-367 Handle Google login primary domain changes

[tommoor]

Unfortunately this is due to the fact that Google uses the domain name as the primary ID. An awful decision that continues to bite everyone that uses it as an auth provider forever.

If you want to easily fix your setup without code changes the easiest thing to do is to find the authentication_provider record in the db and change the providerId to your new domain name.

In a self-hosted environment if the domain matches one in allowed domains we could probably continue to allow sign-in by switching the user authentication to the other provider automatically (the "auto-migrate" mentioned in the comment above)