Staging environments PRIVACY_BUDGET_AUTHORIZATION_ERROR
Closed this issue · 2 comments
Hi team,
We enrolled https://ebayadservices.com/ as our production environment a few weeks ago, and confirmed with your team that it was completed.
![image](https://private-user-images.githubusercontent.com/48471702/332639602-6c31af0b-3133-448c-be04-573cda3213ee.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjE2Nzc0NTUsIm5iZiI6MTcyMTY3NzE1NSwicGF0aCI6Ii80ODQ3MTcwMi8zMzI2Mzk2MDItNmMzMWFmMGItMzEzMy00NDhjLWJlMDQtNTczY2RhMzIxM2VlLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MjIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzIyVDE5MzkxNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTRjNjU5YTQwOGQ0ZTQ1YjRiY2MxMTdiMTk3ZGM2Y2FiZDE0MTE0MzE2OGRjMzIxNDllNzY3OTg1MzcxYTlkNjkmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.v3cZmI11VoiiaEvvtgfBw8yU1NrpZIOFHZHvNKLPjkE)
and we noticed this sentence on your document: Your staging, beta, QA and test environments will be automatically enrolled if they use the same site as your production environment.
However, when we use https://staging.ebayadservices.com/ to do the tests, the job failed to pass the authorization. Could you please help to investigate this issue?
BTW, because our company’s testing environment does not allow external sites, we use a internal proxy to access https://staging.ebayadservices.com/. I don't know if this is the root cause of this issue.
The avro files:
report avro
domain avro
The api response are as followed.
{
"job_status": "FINISHED",
"request_received_at": "2024-05-22T02:15:53.301731Z",
"request_updated_at": "2024-05-22T02:16:02.790976116Z",
"job_request_id": "test11",
"input_data_blob_prefix": "output/output_regular_reports_2024-05-21T19:12:54-07:00.avro",
"input_data_bucket_name": "tracking_tf_state_bucket",
"output_data_blob_prefix": "output/summary_report.avro",
"output_data_bucket_name": "tracking_tf_state_bucket",
"postback_url": "",
"result_info": {
"return_code": "PRIVACY_BUDGET_AUTHORIZATION_ERROR",
"return_message": "com.google.aggregate.adtech.worker.exceptions.AggregationJobProcessException: Aggregation service is not authorized to call privacy budget service. This could happen if the createJob API job_paramaters.attribution_report_to does not match the one registered at enrollment. Please verify and contact support if needed. \n com.google.aggregate.adtech.worker.aggregation.concurrent.ConcurrentAggregationProcessor.consumePrivacyBudgetUnits(ConcurrentAggregationProcessor.java:451) \n com.google.aggregate.adtech.worker.aggregation.concurrent.ConcurrentAggregationProcessor.process(ConcurrentAggregationProcessor.java:329) \n com.google.aggregate.adtech.worker.WorkerPullWorkService.run(WorkerPullWorkService.java:142)\nThe root cause is: com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngine$TransactionEngineException: PRIVACY_BUDGET_CLIENT_UNAUTHORIZED \n com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngineImpl.createTransactionEngineException(TransactionEngineImpl.java:203) \n com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngineImpl.proceedToNextPhase(TransactionEngineImpl.java:67) \n com.google.scp.operator.cpio.distributedprivacybudgetclient.TransactionEngineImpl.executeDistributedPhase(TransactionEngineImpl.java:196)",
"error_summary": {
"error_counts": [],
"error_messages": []
},
"finished_at": "2024-05-22T02:16:02.778068915Z"
},
"job_parameters": {
"output_domain_blob_prefix": "domain/output_local_domain.avro",
"output_domain_bucket_name": "tracking_tf_state_bucket",
"attribution_report_to": "https://staging.ebayadservices.com"
},
"request_processing_started_at": "2024-05-22T02:15:55.674601807Z"
}
Hi Yang, we are actively looking into this specific issue and will be in touch through our support.
Hi @ruclohani ,
Thanks for your reply. Looking forward to message about your successful fix! Much appreciated.