Skip to main content
Solved

Connecting Chrome browser management logs with Chronicle

  • April 18, 2024
  • 6 replies
  • 42 views

Forum|alt.badge.img+2

Hey all,

I am trying to connect our Chrome browser with Chronicle using the native workspace connector and Chronicle ingestion API. For some reason, i am not able to get the API key to work with the connector. The ingestion API key works since i have tested it with native python script we get from google documentation here .

Is there a specific way we have provide the API key for the Chrome connector to work? Also i cant seem to find the configuration ID for the connector as well.

Here is the documentation i am following.

https://cloud.google.com/chronicle/docs/ingestion/default-parsers/collect-chrome-management

 

Best answer by mikewilusz

This connector leverages our ingestion v1 API keys (non-JSON). You can reach out to support or your CSM to have one provisioned and provided.

-mike

6 replies

cmorris
Staff
Forum|alt.badge.img+10
  • Staff
  • April 18, 2024

You should be able to find the Configuration ID on the Users & browsers settings page and the Connectors page. Has a Provider Configuration been created? If not, check here on how to create one - https://support.google.com/chrome/a/answer/11375053?sjid=9443799980930871339-NA


Forum|alt.badge.img+2
  • Author
  • Bronze 1
  • April 18, 2024

Thanks very much for the response, thats exactly where i am running into the issue. When i create the provider configuration, its asking for the API key and host name. 

My question is, how do i enter the API key? Would be the whole json file or just the private key from the json file? I have tried every possible option and none seem to work.

Also what would be the host name, do i enter the ingestion API URL(https://malachiteingestion-pa.googleapis.com) or is there something else. The documentation points to the configuration ID but i cant seem to find that anywhere on the workspace? Would be great if you can point me to the right direction. 

Thanks again

 


mikewilusz
Staff
Forum|alt.badge.img+10
  • Staff
  • Answer
  • April 18, 2024

This connector leverages our ingestion v1 API keys (non-JSON). You can reach out to support or your CSM to have one provisioned and provided.

-mike


Forum|alt.badge.img+2
  • Author
  • Bronze 1
  • April 19, 2024

This connector leverages our ingestion v1 API keys (non-JSON). You can reach out to support or your CSM to have one provisioned and provided.

-mike


Thanks for the quick response, let me reach out to the CSM.

 


dnehoda
Staff
Forum|alt.badge.img+16
  • Staff
  • April 19, 2024

Thanks for the quick response, let me reach out to the CSM.

 


I’m assuming you don’t have a CSM - so a support case would be the path here.  


Forum|alt.badge.img+2
  • Author
  • Bronze 1
  • April 24, 2024

This connector leverages our ingestion v1 API keys (non-JSON). You can reach out to support or your CSM to have one provisioned and provided.

-mike


I needed the ingestion v1 APi and it worked. Thanks all