If you disable the registration flow in Ory Kratos and a user tries to sign in through Google (OIDC) but no associated account exists, the user will not be able to register a new account via Google. Since registration is disabled, Kratos will not create a new identity for the user, and the login attempt will fail. The knowledge sources confirm that Ory Kratos supports both login and registration via OIDC (e.g., Google), but these are controlled by enabling or disabling the respective flows in the configuration. If registration is disabled, only existing users can log in; new users cannot register, even via social sign-in. The system will not create a new account for a user signing in with Google if no account exists, and the login will not succeed. The user may see an error or be redirected to the login UI, but no new identity will be created in this scenario. This is consistent with the documented behavior for registration and login flows and the handling of OIDC methods in Ory Kratos[Registration Flow Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-registration), [Login Flow Documentation](https://www.ory.sh/docs/kratos/self-service/flows/user-login). If you need to allow new users to sign up via Google, the registration flow must be enabled.