You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Google Chat is an intelligent and secure communication and collaboration tool, built for teams.
14
14
@@ -29,6 +29,44 @@ To send rich text messages, use the Create Message action with `Disable HTML` in
29
29
30
30
## Google Chat configuration
31
31
32
+
Our Google Chat integration support two types of authentication, Service Account and WIF (Workload Identity Federation). We recommend using WIF since it is more secure and easier to manage. For more information, see [Workload Identity Federation](https://cloud.google.com/iam/docs/workload-identity-federation).
33
+
34
+
## Required AWS details from Sumo Logic
35
+
36
+
To configure the Google Chat integration using WIF authentication, you need the following AWS details from Sumo Logic. These details are essential for setting up the Workload Identity Federation (WIF) credentials in Google Workspace:
To [create WIF credentials](https://cloud.google.com/iam/docs/workload-identity-federation) in Google Workspace needed to configure the Google Chat app integration, follow these steps:
46
+
1. Log in to the [Google Cloud](https://console.cloud.google.com) portal.
47
+
2. Select a Google Cloud project (or create a new one).
48
+
3. Go to the **API&Services**
49
+
4. In the same page click on **ENABLED API AND SERVICES** and search for Google Chat and enable it.
50
+
5. Go to the **IAM & Admin** > **Service Accounts** page.
51
+
6. Click **CREATE SERVICE ACCOUNT**[Service Account](https://cloud.google.com/iam/docs/service-accounts-create) is required to access the Google Chat API.
52
+
7. While creating the service account, in **Permissions** add the role **Service Account Token Creator** and click on **DONE**. <br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/google-chat/google-chat-11.png')} style={{border:'1px solid gray'}} alt="google-chat" width="800"/>
53
+
8. Go to the **IAM & Admin** > **Workload Identity Federation** page. <br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/google-chat/google-chat-4.png')} style={{border:'1px solid gray'}} alt="google-chat" width="800"/>
54
+
9. Click **CREATE POOL**, provide the details, and click on **CONTINUE**. <br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/google-chat/google-chat-5.png')} style={{border:'1px solid gray'}} alt="google-chat" width="800"/>
55
+
10. Add **Provider details**. Select **AWS** as the provider type and provide the details of the AWS Account ID which is provided by Sumo Logic. Click on **CONTINUE** and **SAVE**. <br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/google-chat/google-chat-6.png')} style={{border:'1px solid gray'}} alt="google-chat" width="800"/>
56
+
11. Now you will see the created pool and provider. <br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/google-chat/google-chat-8.png')} style={{border:'1px solid gray'}} alt="google-chat" width="800"/>
57
+
12. Now we have to build a principal name to configure in Sumo Logic. The format of the principal name is: `principalSet://iam.googleapis.com/projects/{YourProjectID}/locations/global/workloadIdentityPools/{YourPoolName}/attribute.aws_role/arn:aws:sts::{SumoAWSAccountID}:assumed-role/{SumoAWSRole}/{SumoAWSLambdaFunction}`.
58
+
13. Go to the **IAM & Admin** > **IAM** page and click on **Grant Access** to add a new principal.
59
+
14. In the **New principals** field, provide the above principal name and select the role **Workload Identity User**. Click on **SAVE**. <br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/google-chat/google-chat-12.png')} style={{border:'1px solid gray'}} alt="google-chat" width="800"/>
60
+
15. Go to the **IAM & Admin** > **Workload Identity Federation** page and select the pool which was created above.
61
+
16. Click on **Grant Access** > **Grant access using service account impersonation**.
62
+
17. Select the service account which created above, select the principle as aws_role and provide the arn `arn:aws:sts::{SumoAWSAccountID}:assumed-role/{SumoAWSRole}` and click on **SAVE**. <br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/google-chat/google-chat-10.png')} style={{border:'1px solid gray'}} alt="google-chat" width="800"/>
63
+
18. Again go to **Grant Access** > **Grant access using service account impersonation**. Select the service account which was created above. Select the principle as `aws_role` and provide the arn `arn:aws:sts::{SumoAWSAccountID}:assumed-role/{SumoAWSRole}/{SumoAWSLambdaFunction}`. Click on **SAVE**.
64
+
19. Download the WIF `conf.json` file. Make sure you save it in a safe place. Use the JSON content to configure the Google Chat integration to use WIF authentication in Automation Service and Cloud SOAR.
65
+
20. To configure the app in Google Chat API, go to **APIs & Services**, select **Google Chat API**, and in **CONFIGURATION** provide the details and click on **SAVE**. <br/><img src={useBaseUrl('/img/platform-services/automation-service/app-central/integrations/google-drive/google-drive-10.png')} style={{border:'1px solid gray'}} alt="google-drive" width="800"/>
66
+
21. Go to the **Google Chat App** and add the above app in that. Also, to add above app in space, go to **space** and in **Apps & integration** add the app.
67
+
68
+
69
+
### Service Account authentication
32
70
To [create service account credentials](https://developers.google.com/workspace/guides/create-credentials) in Google Workspace needed to configure the Google Chat app integration, follow these steps:
33
71
34
72
1. Log in to the [Google Cloud](https://console.cloud.google.com) portal.
@@ -83,4 +121,5 @@ Use Google Chat to receive notifications, ensuring you promptly get important up
83
121
84
122
* August 27, 2024 (v2.0) - First upload
85
123
* October 29, 2024 (v2.0) - Updated the docs
86
-
* December 06, 2024 (v2.1) - Added the Rich Text Message support in the Create Message action
124
+
* December 06, 2024 (v2.1) - Added the Rich Text Message support in the Create Message action
125
+
* September 25, 2025 (v2.2) - Updated the WIF configuration steps
0 commit comments