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
  • Okta configuration
  • 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

Okta

Use these instructions to set up Okta as your SSO provider for Tonic Structural.

Okta configuration

You complete the following configuration steps within Okta:

  1. Create a new application. Choose the OIDC - OpenId Connect method with the Single-Page Application option.

  2. Click Next, then fill out the fields with the values below:

    • App integration name: The name to use for the Ephemeral application. For example, Ephemeral, Ephemeral-Prod, Ephemeral-Dev.

    • Grant type: Implicit (hybrid)

    • Sign-in redirect URIs: <base-url>/sso/callback/okta

    • Sign-out redirect URIs: <base-url>/sso/logout

    • Base URIs: The URL to your Ephemeral instance

    • Controlled access: Configure as needed to limit Ephemeral access to the appropriate users

  3. After saving the above, navigate to the General Settings page for the application and make the following changes:

    1. Grant type: Check Implicit (Hybrid) and Allow ID Token with implicit grant type.

    2. Login initiated by: Either Okta or App

    3. Application visibility: Check Display application icon to users

    4. Initiate login URI: <base-url>

Ephemeral configuration

After you complete the configuration in Okta, uncomment and configure the following values in the Ephemeral helm chart.

In values.yaml:

# Okta SSO Config
# -----------------
sso:
  isEnabled: true
  okta:
    clientId: <client-id>
    domain: <sso-domain>
    identityProviderId: <identity-provider-id>
    authorizationServerId: <customer auth server if you have one>
PreviousGoogleNextSetting the registry location for data volumes

Last updated 9 months ago

Was this helpful?