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

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 begin to configure the Google Cloud Identity 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 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 sign 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.