[🔒] NT-693 Adding client_id param to Lake requests #725
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
📲 What
Sending the client ID as a query param of requests to the Lake endpoint.
🤔 Why
SECURITY
🛠 How
clientId
intoLakeBackgroundService
and passed it intoLakeService.track
that's annotated as aQuery
named"client_id"
👀 See
An extremely redacted request log:

📋 QA
We don't currently test our network clients but I believe there is a ticket in the backlog.
Please check your friendly Logcat 🐱 on a debug build of the app for the Lake requests. The URL should contain a
client_id
query param.Story 📖
NT-693