Skip to content

Conversation

BeltranBulbarellaDD
Copy link
Contributor

@BeltranBulbarellaDD BeltranBulbarellaDD commented Jul 22, 2025

Motivation

After incident-40275 where a customer's Extensions API Key was exposed. There was a security concern that this API would allow unauthorized data submission to Datadog from the customer's chrome extension.

Changes

When there is no allowedTrackingOrigins configured and isUnsupportedExtensionEnvironment is true we throw a console error and prevent the start of the SDK.

Test instructions

Previous unit and e2e test should suffice.
If not, run locally a browser extension without allowedTrackingOrigins, the SDK should throw a console error and not initiate.
Add the parameter with a valid url and everything should work as normal.

Checklist

  • Tested locally
  • Tested on staging
  • Added unit tests for this change.
  • Added e2e/integration tests for this change.

…ironment and no allowedTrackingOrigins is provided
@BeltranBulbarellaDD BeltranBulbarellaDD changed the title Update isAllowedTrackingOrigins to return false when in extension env… [RUM-10952] Make allowedTrackingOrigins required in Browser Extensions Jul 22, 2025
@BeltranBulbarellaDD BeltranBulbarellaDD changed the title [RUM-10952] Make allowedTrackingOrigins required in Browser Extensions 💥 [RUM-10952] Make allowedTrackingOrigins required in Browser Extensions Jul 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant