LogoLogo
Release notesAPI docsDocs homeEphemeral CloudTonic.ai
  • Tonic Ephemeral guide
  • About Tonic Ephemeral
  • Getting started with the Ephemeral free trial
  • Managing your Ephemeral account
  • Managing Databases
    • Viewing the list of databases
    • Starting a database
    • Changing the database configuration
    • Database configuration settings
      • Setting the required resources for a database
      • Setting the database expiration
      • Providing a custom configuration file
    • Connecting to a database
    • Resetting a database
    • Deactivating and reactivating databases
    • Managing auto snapshots
    • Tracking database activity
    • Deleting a database
  • Managing user snapshots
    • About user snapshots
    • Viewing the user snapshot list
    • Creating a user snapshot from an Ephemeral database
    • Creating a user snapshot from imported data
    • Editing a user snapshot
    • Creating a database from a user snapshot
    • Deleting a user snapshot
  • Installing and configuring Ephemeral
    • Ephemeral architecture
    • Configuring an allowlist for Ephemeral Cloud database connections
    • Installing a self-hosted instance of Ephemeral
      • System requirements
      • Deploying Ephemeral with Helm
    • Configuring database access on a self-hosted instance
    • Configuring tolerations and node selectors
    • Managing access to Ephemeral
      • Managing Ephemeral users
      • Enabling SSO on a self-hosted instance
        • Google
        • Okta
    • Setting the registry location for data volumes
    • Managing custom images
      • Creating, editing, and deleting custom images
      • Oracle image configuration
    • Configuring automatic deletion of snapshots
  • Monitoring and data collection
    • Monitoring your Ephemeral billed usage
    • Monitoring your disk storage
    • Data that Tonic.ai collects
  • Using the Ephemeral API
    • About the Ephemeral API
    • Configuring Ephemeral
    • Getting information about Ephemeral databases
    • Starting a database
    • Managing databases
    • Managing snapshots
Powered by GitBook
On this page
  • Create an OAuth 2.0 client ID in Google
  • Ephemeral configuration

Was this helpful?

Export as PDF
  1. Installing and configuring Ephemeral
  2. Managing access to Ephemeral
  3. Enabling SSO on a self-hosted instance

Google

PreviousEnabling SSO on a self-hosted instanceNextOkta

Last updated 10 months ago

Was this helpful?

Use these instructions to set up Google as your SSO provider for Tonic Ephemeral.

Create an OAuth 2.0 client ID in Google

  1. Go to

  2. Click Create credentials, located near the top.

  3. Select OAuth client ID.

  4. Select Web application as the application type.

  5. Choose a name.

  6. Under Authorized redirect URIs, add the URL of the Ephemeral server with the endpoint /sso/callback. For example, for a local Ephemeral server at http://localhost:3000, you would need to set the redirect URL tohttp://localhost:3000/sso/callback. Also note that internal URLs might not work.

  7. On the confirmation page, note the client ID and client secret. You will need to provide them to Ephemeral.

Ephemeral configuration

After you complete the configuration in Google, you uncomment and configure the following values in the Ephemeral Helm chart.

  • The client ID

  • The client secret

In values.yaml:

# Google SSO Config
# -----------------
sso:
  isEnabled: true
  google:
    clientId: <client-id>
    clientSecret: <client-secret>
https://console.developers.google.com/apis/credentials