Skip to main content

Team,

I am in the process of deploying Google Chronicle in our organization and following the instructions provided in the official documentation at the following link: https://cloud.google.com/chronicle/docs/onboard/configure-authentication?hl=es-419#plan_workforce_identity  

However, I have encountered an issue that I am unable to resolve on my own. In our Chronicle tenant, accessible at https://xxxx.backstory.chronicle.security/ , there is no evidence of an organization in the project with the "ORGANIZATION_ID" corresponding to the domain.

This issue is preventing us from proceeding with the authentication configuration step, which requires an organization to be set up in the mentioned project. We would greatly appreciate your help and collaboration in resolving this issue.

Steps We Have Followed:
Accessed the Chronicle tenant.
Reviewed the authentication configuration documentation.
Verified the existence of an organization in the project with the "ORGANIZATION_ID".

Shot:

 


Shot:

 


Based upon this screenshot, it appears you're using a non-org Google Cloud environment. You can read details here about how to provision an organization: https://cloud.google.com/resource-manager/docs/creating-managing-organization


Having an organization within GCP is required to use SecOps with Workforce Identity.


-mike


Hi pable_vallejo,


It sounds like that you have validated the existence of your project. Here are a few other troubleshooting steps you might follow:



  • Refresh and validate: Refresh your Chronicle tenant and wait a few minutes to see if it appears

  • Clear Cache and Cookies: Sometimes, browser cache can cause issues. Try clearing your cache and cookies and then access your Chronicle tenant again.

  • Check domain verification: In your Google Workspace Admin console, navigate to "Account" > "Domains". Make sure your domain shows a "Verified" status. If not, follow the steps to verify it.

  • Confirm Organization ID: Go to the Google Workspace Admin console and navigate to "Security" > "API Controls". Find the "Organization ID" listed there and ensure it matches what you're using in Chronicle.

  • Contact Support: If none of the above solutions work, reach out to Google Cloud Support for assistance. They can check the backend configuration and help troubleshoot further.


Hope this helps


Reply