Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: add hashed_fxa_uid to HawkPayload #1613

Merged
merged 5 commits into from
Oct 21, 2024

Conversation

taddes
Copy link
Contributor

@taddes taddes commented Oct 18, 2024

Description

As part of Sync’s authentication flow, Hawk Authentication is used to verify message integrity and authenticity. The HawkPayload is generated within Tokenserver and passed to the Syncserver. This contains required fields related to the authorized user/account that is syncing.

Presently, the HawkPayload in Sync does not process or use the hashed_fxa_uid. We would like this value as part of our DAU measurement, as it is a way of discerning unique sync usage that is not attributable.

This requires passing the value to the HawkPayload from Tokenserver and moving it through the intermediate HawkIdentifier struct and over into the UserIdentifier struct, which exposes the value within the MetaRecord.

Testing

Internal unit tests

Issue(s)

Closes SYNC-4442.

@taddes taddes self-assigned this Oct 18, 2024
@taddes taddes force-pushed the feat/modify-hawk-payload-fxa-id-SYNC-4442 branch from afa74d7 to 7315842 Compare October 18, 2024 18:09
@taddes taddes marked this pull request as ready for review October 18, 2024 18:57
@taddes taddes changed the title add hashed_fxa_uid to HawkPayload struct and tests feat: add hashed_fxa_uid to HawkPayload Oct 21, 2024
@taddes taddes merged commit 715cf95 into master Oct 21, 2024
8 checks passed
@taddes taddes deleted the feat/modify-hawk-payload-fxa-id-SYNC-4442 branch October 21, 2024 23:41
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.

2 participants