Configure whether end users can sign in to your app with a social identity provider, such as Google, Microsoft, Facebook, or Apple. This is the CLI equivalent of toggling social login options in your app’s authentication settings. This command updates your local auth config file. To apply the change to your deployed app, runDocumentation Index
Fetch the complete documentation index at: https://docs.base44.com/llms.txt
Use this file to discover all available pages before exploring further.
auth push or deploy.
Usage
Enable a social login provider:Arguments
| Argument | Description | Required |
|---|---|---|
<provider> | Social login provider: google, microsoft, facebook, or apple | Yes |
<enable|disable> | Whether to enable or disable the provider | Yes |
Flags
The following flags configure custom OAuth credentials. They are currently supported for Google only. Other providers use Base44-managed credentials.| Flag | Description |
|---|---|
--client-id <id> | Custom OAuth client ID. |
--client-secret <secret> | Custom OAuth client secret. |
--client-secret-stdin | Read the client secret from stdin. |
--env-file <path> | Read the client secret from a .env file. The file must contain a google_oauth_client_secret key. |
See also
auth password-login: Enable or disable email and password loginauth pull: Fetch auth config from Base44 to your local projectauth push: Push local auth config to Base44secrets set: Set project secrets manuallydeploy: Deploy all project resources, including auth config- Managing login and registration: Configure login options in the dashboard

