Stay organized with collections
Save and categorize content based on your preferences.
NAME
gdcloud auth login - Authorize the gdcloud CLI to sign in with the configured identity provider.
SYNOPSIS
gdcloud auth login [flags]
DESCRIPTION
Authorize the gdcloud CLI to sign in with the configured identity provider.
The command authenticates with the current organization.
Run the command again after switching organizations.
It requires that the certificate authority (CA) certificate for the login config is installed
in the trusted certificates store.
If the CA certificate is not installed, use the --login-config-cert flag to specify the path
to find the CA certificate.
It requires a browser to exist on the device.
EXAMPLES
To sign in with the configured identity provider, run:
gdcloud auth login
OPTIONAL FLAGS
--login-config-cert string (Optional) Absolute file path to the CA certificate file to be used for fetching login-config over HTTPS connection
--no-browser (Optional) Use this flag to authenticate the gdcloud CLI on a machine without a web browser.
--skip-kubeconfig-update (Optional) Skip updating the kubeconfig file for management API servers.
GDCLOUD WIDE FLAGS
These flags are available to all commands: --configuration, --format, --help, --project, --quiet.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-09-04 UTC."],[[["\u003cp\u003eThe \u003ccode\u003egdcloud auth login\u003c/code\u003e command authorizes the gdcloud CLI to sign in with the configured identity provider for the current organization.\u003c/p\u003e\n"],["\u003cp\u003eRe-running the command is necessary after switching organizations to re-authenticate with the newly selected organization.\u003c/p\u003e\n"],["\u003cp\u003eA CA certificate must be installed in the trusted certificates store, or the \u003ccode\u003e--login-config-cert\u003c/code\u003e flag can be used to specify its path.\u003c/p\u003e\n"],["\u003cp\u003eA web browser is typically required for this process, unless using the \u003ccode\u003e--no-browser\u003c/code\u003e flag to authenticate from a separate device.\u003c/p\u003e\n"]]],[],null,["# gdcloud auth login\n\nNAME\n----\n\ngdcloud auth login - Authorize the gdcloud CLI to sign in with the configured identity provider.\n\nSYNOPSIS\n--------\n\n gdcloud auth login [flags]\n\nDESCRIPTION\n-----------\n\nAuthorize the gdcloud CLI to sign in with the configured identity provider.\nThe command authenticates with the current organization.\nRun the command again after switching organizations.\nIt requires that the certificate authority (CA) certificate for the login config is installed\nin the trusted certificates store.\nIf the CA certificate is not installed, use the --login-config-cert flag to specify the path\nto find the CA certificate.\nIt requires a browser to exist on the device.\n\n### EXAMPLES\n\n To sign in with the configured identity provider, run:\n\n gdcloud auth login\n\n### OPTIONAL FLAGS\n\n --login-config-cert string (Optional) Absolute file path to the CA certificate file to be used for fetching login-config over HTTPS connection\n --no-browser (Optional) Use this flag to authenticate the gdcloud CLI on a machine without a web browser.\n --skip-kubeconfig-update (Optional) Skip updating the kubeconfig file for management API servers.\n\n### GDCLOUD WIDE FLAGS\n\nThese flags are available to all commands: `--configuration`, `--format`, `--help`, `--project`, `--quiet`.\n\nFor more information, see the [gdcloud CLI reference overview](/distributed-cloud/hosted/docs/latest/appliance/resources/gdcloud-reference/gdcloud) page."]]
