This file contains ambiguous Unicode characters

This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.

Table of contents

• Default credentials
• Key file
• Web browser
• OAuth (Pregenerated)

DBeaver supports Google Cloud IAM authentication.

Depending on how you authenticate in Google Cloud, choose one of the following credential types.:

Default credentials

Use Default credentials to let Google Cloud find your credentials automatically. It looks through the following sources in order:

1. Environment variable GOOGLE_APPLICATION_CREDENTIALS
2. Active GCP CLI session
3. Shared user or service credentials file (for example, application_default_credentials.json in AppData)
4. Google Compute Engine metadata

This is the easiest option if you already use GCP CLI or your system is configured with SSO or web identity credentials.

For details, see the GCP authentication guide.

Key file

Select Key file to manually provide a path to your credentials JSON file. This file contains private keys and authentication details for a user or service account.

You can create or download a key file in the Google Cloud Console. For details, see Create and manage service account keys.

Web browser

Select Web browser if your GCP account uses a web-based or SSO login. You’ll be redirected to the Google authorization page to sign in and grant access.

This option uses the standard OAuth 2.0 web server flow to authenticate and obtain access tokens.

OAuth (Pregenerated)

Use OAuth (Pregenerated) when you already have an existing OAuth setup. Enter the following values:

• Client ID – the OAuth client identifier
• Client Secret – the client secret associated with your OAuth client
• Refresh Token – a token that allows the product to refresh access automatically

For more details, see OAuth application integration.