chore: update proton and remove deprecated billing account org_id usage #1336
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.
Problem
The protobuf schema deprecated
org_id,billing_id, andproject_idfields in several billing account API requests because the backend can infer these IDs from other parameters (e.g.,org_idcan be inferred frombilling_account_id). However, the backend was still accepting and using these deprecated fields from client requests, creating a security risk where clients could potentially manipulate these IDs.Solution
This PR removes all usage of deprecated fields and implements server-side inference of IDs for security:
org_idfrom requests:UpdateBillingAccount: Now infers org_id from billing account IDUpdateBillingAccountDetails: Fetches customer to get org_id for audit logbilling/customer/service.go: Always uses existing customer's org_id instead of requestgetOrgForBillingAccounthelper that fetches org_id from billing accountSecurity Impact
Test plan