Shared Signals with Google Workspace Beta
Receiving shared signals in Google Workspace is a closed beta at Google, available to Google Workspace Enterprise Plus customers who are admitted to it. On the XFA side, Shared Signals is in beta and turned on per organization on request (see the overview).
Note: This guide assumes that you have an account set up with XFA for your organization and that you're an administrator for that organization on XFA and a super administrator in the Google Admin console. If you do not have an account, you can create one at https://dashboard.xfa.tech/signup.
What Google does
Google's receiver only supports the CAEP session-revoked event. When a device of your organization becomes not compliant (see what "not compliant" means), XFA sends Google a session-revoked event for the user, and Google signs the user out of Google Workspace. When the device becomes compliant again, nothing is sent: the user simply signs in again.
A revoked session only keeps the device out when the next sign-in is checked by XFA. Set up XFA as the identity provider for Google Workspace for the users you cover; otherwise the user signs back in on the same, non-compliant device.
1. Request access at Google
Ask your Google account team to admit your Workspace tenant to the Shared Signals receiver beta, naming XFA as the transmitter. Google will tell you where in the Admin console the transmitter is configured once you are admitted.
2. Add the Google Workspace connection in XFA
- In the XFA dashboard, open Device security > Shared Signals.
- Click Add connection.
- Enter a Name, for example
Google Workspace, and choose Google Workspace as the Receiver. - Click Add connection.
- Copy the token from the dialog. It is shown once; if you lose it, use Rotate token on the connection and enter the new token at Google.
In the Transmitter section at the top of the page, copy the Transmitter URL (https://ssf.xfa.tech) and the Well-known configuration URL (https://ssf.xfa.tech/.well-known/ssf-configuration).
3. Add XFA as a transmitter at Google
In the Google Admin console, register XFA as a Shared Signals transmitter with the well-known URL and the token from the previous step. Google creates the stream with XFA and sends XFA its delivery endpoint.
The events XFA sends to Google are addressed to the audience Google requires:
https://sharedsignals.googleapis.com
You do not have to set this yourself; it is the default for a Google Workspace connection. The user in each event is identified by email, so the user's email in XFA must match the Google Workspace account.
Once Google has created the stream, it appears under the connection on the Shared Signals page, with its status and the time and result of the last delivery.
4. Verify with a test event
On the Shared Signals page, find the stream under your Google Workspace connection and click Send test event. XFA pushes an SSF verification event through the stream and shows the result of the delivery on the stream.
To see a real revocation, let a device of a test user fail a check that blocks in a policy attached to one of your applications: within minutes the user is signed out of Google Workspace, and signing in again through XFA is blocked until the device is fixed.
Troubleshooting
- The stream shows a failed delivery: the stream shows the error Google returned. Deliveries are retried on temporary errors.
- Google cannot connect to XFA: check the well-known URL and the token. A rotated token replaces the previous one at once, so enter the new token at Google.
- The user is not signed out: check that the user's email in XFA matches the Google account and that the failing check is set to block in a policy that is attached to an application. Google only receives
session-revoked, so a device that merely warns sends nothing. - The user signs back in on the same device: Google Workspace sign-in for that user does not go through XFA. See the warning above.