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 https://console.developers.google.com/apis/credentials

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>

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>

On Ephemeral Cloud, users who have a corporate Google email address can use the built-in Google single sign-on (SSO) configuration to sign up for and log into Ephemeral.

You can also enable SSO on a self-hosted instance. Tonic Ephemeral respects the access control policy of your single sign-on (SSO) provider. To access Ephemeral, users must be granted access to the Ephemeral application within your SSO provider.

To enable SSO on your self-hosted instance, you first complete the required configuration in the SSO provider. You then configure Ephemeral to connect to it.

After you enable SSO, users can use SSO to create an account in Ephemeral.

To only allow SSO authentication, in your Helm chart, set sso.isRequired to true.

For self-hosted instances, Ephemeral supports the following SSO providers: