IssueTracker

This will create a feature request which anybody can view and comment on.

Please describe your requested enhancement. Good feature requests will solve common problems or enable new use cases.

What you would like to accomplish:
Add more information as to why Scheduler jobs fail with a 401 error beyond "UNAUTHENTICATED"

How this might work:
Provide the name of the service account where the process fails, indicate any missing roles, indicate if an OIDC token is not set up correctly

If applicable, reasons why alternative solutions are not sufficient:
The current sanitized error message [1]  makes it harder to debug issues with authentication with HTTP triggered Cloud Functions / HTTP targets for Cloud Run

[1] {
"insertId": "",
"jsonPayload": {
"url":
"https://project.cloudfunctions.net/Function",
"targetType": "HTTP",
"jobName":
"projects/project/locations/location/jobs/schedulerJob",
"@type":
"type.googleapis.com/google.cloud.scheduler.logging.AttemptFinished",
"status": "UNAUTHENTICATED"
},
"httpRequest": {
"status": 401
},
"resource": {
"type": "cloud_scheduler_job",
"labels": {
"location": "",
"project_id": "",
"job_id": ""
}

Other information (workarounds you have tried, documentation consulted, etc):
[2] https://cloud.google.com/scheduler/docs/http-target-auth#create_a_scheduler_job_with_authentication