base44 auth social-login
Enable or disable social login providers for your app (Google, Microsoft, Facebook, Apple). Auth config changes are local until you runbase44 auth push or base44 deploy.
Syntax
Arguments
| Argument | Description | Required |
|---|---|---|
<provider> | Social login provider: google, microsoft, facebook, apple | Yes |
<action> | enable or disable | Yes |
Options
| Option | Description | Required |
|---|---|---|
--client-id <id> | Custom OAuth client ID (Google only) | No |
--client-secret <secret> | Custom OAuth client secret (Google only) | No |
--client-secret-stdin | Read client secret from stdin (Google only) | No |
--env-file <path> | Read client secret from a .env file using key google_oauth_client_secret (Google only) | No |
--client-id, --client-secret, --client-secret-stdin, --env-file) are only supported for Google. For other providers, enable/disable without any options.
Examples
Notes
- Changes are written to the local
base44/auth/config. Runnpx base44 auth pushornpx base44 deployto apply them. - SSO and social login are mutually exclusive — enabling social login disables any active SSO configuration in the local auth config (and vice versa).
- Disabling the last active login method will warn that users will be locked out.
- When using custom OAuth for Google:
--client-idis required whenever any secret option is passed. - The client secret is saved to Base44’s secrets store; the client ID is stored in the local auth config.
- If you set a custom client ID without providing a secret now, push the secret later:
npx base44 secrets set --env-file <path>
Related Commands
| Command | Description |
|---|---|
base44 auth password-login | Enable or disable username & password authentication |
base44 auth sso | Configure SSO identity provider |
base44 auth push | Push local auth config to Base44 |
base44 auth pull | Pull auth config from Base44 |

