microsoft / microsoft/azure-devops-auth-samples
PATCH request response with expired token
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 277
- Forks
- 307
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 2
Description
Hey there,
I was wondering what is supposed to be the expected response when making a PATCH request with an expired bearer token on api version 5.0.
The response body I am getting is:
{
"eventId": 3000,
"$id": "1",
"errorCode": 0,
"typeName": "Microsoft.TeamFoundation.Framework.Server.UnauthorizedRequestException, Microsoft.TeamFoundation.Framework.Server",
"innerException": null,
"message": "TF400813: The user '' is not authorized to access this resource.",
"typeKey": "UnauthorizedRequestException"
}
with a 401 status code. I ask because this is different from a POST and GET request where we receive a 203 status code when the access token is expired.
Here's a thread with Azure DevOps Support for more context: https://developercommunity.visualstudio.com/content/problem/972334/inconsistent-tf400813-the-user-is-not-authorized-t.html
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No repository file or test is named. Start by reviewing the linked Azure DevOps Support thread and compare the documented PATCH response with the reported POST and GET behavior; done would require a clear expected response and a repository change or documentation target.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, javascript
- Domain
- api, authentication
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100