Procedure

1. Go to chrome://extensions.
2. Toggle on Developer mode.
3. Locate the SAM extension and select service worker.
4. Click the Application tab.
5. Select Storage > Extension Storage.
6. Check the following fields.
   • userInfo: The identity anchor for the plugin. Contains browserOktaUserId and the org URL. Expect a valid browserOktaUserId and orgId value. An empty value means that the user isn't signed in.
   • pendingOauthEvents: The local queue of captured OAuth grant attempts. It's populated after a grant flow, and cleared after an HTTP 202 response.
   • orgUrl: The Okta tenant URL from the Google Admin Console. It matches https://<org>.okta.com.

   The plugin uses a collect-store-flush data collection model. Requests are stored locally in pendingOauthEvents until a batch send. A batch send triggers when either of the following occurs:

   • 10 events are collected in local storage.
   • A 1-hour cycle completes with events older than one hour.

7. Click the Application tab.
8. Select Storage > Extension > StorageLocal.
9. Check the following storage keys.
   • jwkRegisterResp: An object is present, confirming that JWKS registration succeeded.
   • authStatus: The value is TOKEN_OK, confirming that a valid access token was obtained.
   • accessToken: A token string is present. The plugin is authenticated and ready to transmit.
   • pendingOauthEvents: The value is an empty array ([]), confirming that queued events were flushed to Okta.
10. Confirm the batch send in the Network tab.

    This is a successful call sequence:

    1. POST /jwks registers the public key.
    2. POST /token exchanges the registration for an access token.
    3. POST /events transmits telemetry and returns HTTP 202 Accepted.

11. Verify data flow on the ISPM dashboard.

    It can take up to two days for the data to appear.