Skip to content

Changing the handling of client claims to use JSON (#4886) #294

Changing the handling of client claims to use JSON (#4886)

Changing the handling of client claims to use JSON (#4886) #294

Triggered via push August 23, 2024 07:20
Status Failure
Total duration 38s
Artifacts
Call OneBranch ADO Pipeline (CI)
26s
Call OneBranch ADO Pipeline (CI)
Fit to window
Zoom out
Zoom in

Annotations

1 error and 2 warnings
Call OneBranch ADO Pipeline (CI)
{"$id":"1","customProperties":{"Descriptor":null,"IdentityDisplayName":null,"Token":null,"RequestedPermissions":0,"NamespaceId":"00000000-0000-0000-0000-000000000000"},"innerException":null,"message":"Access Denied: The Personal Access Token used has expired.","typeName":"Microsoft.VisualStudio.Services.Security.AccessCheckException, Microsoft.VisualStudio.Services.WebApi","typeKey":"AccessCheckException","errorCode":0,"eventId":3000}
Call OneBranch ADO Pipeline (CI)
The following actions uses node12 which is deprecated and will be forced to run on node16: Azure/pipelines@354dddefceb0b503a61338ca81e4091eae3bc84f. For more info: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/
Call OneBranch ADO Pipeline (CI)
The following actions use a deprecated Node.js version and will be forced to run on node20: Azure/pipelines@354dddefceb0b503a61338ca81e4091eae3bc84f. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/