Docs » About SSO integrations for Splunk Observability Cloud » Configure a Google SSO integration

Configure a Google SSO integration 🔗

Note

The Google SSO integration doesn’t support integration-specific entity IDs.

The Google SSO integration lets users in your Google domain log in to the application using their Google credentials.

Before you begin configuring the Google SSO integration, ensure you have completed the steps in Configure SSO integrations for Splunk Observability Cloud, including the section Name an SSO integration to learn about naming your integrations.

To configure a Google SSO integration, you must be an administrator for your organization. To learn more, see Grant and revoke administrative access.

Note

When you configure the Google SSO integration for a domain, everyone in the domain has access to the organization, even if they have not yet been added as an organization user.

  1. Log in to Splunk Observability Cloud.

  2. In the left navigation menu, select Data Management to open the Integrate Your Data page.

  3. In the integration filter menu, select All.

  4. In the Search field, search for Google Sign-In.

  5. Select the Google Sign-In tile to open the Google Sign-In page.

  6. To add Google SSO for a new domain, click Add Domain.

  7. A Google dialog box appears. Select the email address associated with the Google domain that you want to add. For example, if you select the Google account myAddress@myGoogleDomain.com, you add myGoogleDomain.com as the authenticated domain for logging in.

  8. Exit the dialog box. The domain appears in the list of domains for the Google SSO integration. Anyone who has credentials for that domain can use them to log in to Observability Cloud.

If at least one Google domain has access to your organization, the option to sign in with Google appears on the Observability Cloud login screen. If your organization has a custom URL, the option to sign in with Google also appears on the custom URL login page.

To remove a Google domain’s login access:

  1. Log in to Splunk Observability Cloud.

  2. In the left navigation menu, select Data Management.

  3. Select Add Integration to open the Integrate Your Data page.

  4. In the integration filter menu, select All.

  5. In the Search field, search for Google Sign-In.

  6. Select the Google Sign-In tile to open the Google Sign-In page.

  7. Select the “x” for the domain you want to remove.

Configure a Google Cloud Identity SSO integration 🔗

The Google Cloud Identity (GCI) SSO integration lets users log in to Observability Cloud using their Google Cloud credentials.

Before you proceed, review the section Name an SSO integration to learn about naming your integration.

To configure GCI as an IdP using an Observability Cloud SSO integration, you must be an administrator for your organization and a super-administrator of your Google domain. To learn more, see Grant and revoke administrative access.

The G Suite Administrator Help document topic, developed by Google, describes how to configure the integration.

After you complete these steps, the GCI SSO integration is available to users in your GCI organization. When users log in to Observability Cloud from GCI for the first time, they receive an email containing a link that they must open in order to authenticate. This only occurs the first time the user signs in. Subsequent login attempts don’t require validation.

If you want to turn off the email authentication feature, contact Splunk Observability Cloud support.

Once you have a custom URL configured, your users can continue to log in using their existing username/password pair, or they can use their GCI credentials instead. GCI SSO authentication and Observability Cloud username/password authentication are independent.

Report an issue 🔗

Before you create an issue or open a support request, try gathering the following information:

  • What happened and the impact of the issue.

  • All the steps you’ve followed until the issue appeared.

  • What was the expected outcome.

  • Your attempts to solve the issue, including workarounds.

  • The operating system, runtime or compiler version, libraries, frameworks, and application servers of your environment, including your instrumentation settings.

  • Debug logs and other logs that might help troubleshoot the issue.

To get help, see Splunk Observability Cloud support.