Skip to content

Conversation

@vishalegbert-ttd
Copy link
Contributor

@vishalegbert-ttd vishalegbert-ttd commented Nov 28, 2025

Changes:

  • Add siteKeyId to AdvertisingToken class when decoding token
  • Update token validation to:
    • Check if token's siteKeyId belongs to calling participant
    • Allow validation of any input DII
    • Return validation error if input token is not valid
    • Record metrics of validation results
  • Update /token/validate CORS handler to allow Authorization header from browsers
  • Add metrics to track site keyset status

Testing:

  • Unit tests
  • Deployed to candidate operator, verified metrics are working as expected

Instant.ofEpochMilli(establishedMillis),
Instant.ofEpochMilli(expiresMillis),
new OperatorIdentity(0, OperatorType.Service, 0, masterKeyId),
new PublisherIdentity(siteId, siteKeyId, 0),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we directly use the siteKeyId stored in PublisherIdentity for validation?

@vishalegbert-ttd vishalegbert-ttd merged commit 65ab0b9 into main Dec 3, 2025
9 checks passed
@vishalegbert-ttd vishalegbert-ttd deleted the vse-UID2-6322-allow-any-dii-token-validate branch December 3, 2025 06:00
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.

3 participants