Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The User Is Not Authorized to Access This Resource #488

Open
chtjfi opened this issue Aug 15, 2023 · 3 comments
Open

The User Is Not Authorized to Access This Resource #488

chtjfi opened this issue Aug 15, 2023 · 3 comments

Comments

@chtjfi
Copy link

chtjfi commented Aug 15, 2023

Hello.

We migrated a collection that uses the Team Calendar extension (v 2.0.17) from one server to another, upgrading from Azure DevOps Server 2020 (Dev18.M170.8) to Azure DevOps Server 2022 (AzureDevOpsServer_20221122.1) in the process. After the migration everything is working (so far) on the new server except for the Team Calendar exception. When adding an event the user prompted for credentials to the server to which the user is already authenticated. Supplying the username and password does not get the user past this authentication screen (see attached screenshot).

In the browser's network capture we can see this...

{
"message": "TF400813: The user is not authorized to access this resource. ",
"type": "Microsoft.TeamFoundation.Framework.Server.InvalidIdentityException",
"isRemoteException": false,
"errorCode": 0,
"eventId": 3000
}

AuthenticationDialog

What we tried:

  1. We made the user an administrator on the new Azure DevOps server to see if it was a permission issue. This had no effect.

  2. We brought the collection online on the old server to see if the calendar was trying to reach the old server for some reason. This had no effect.

Thanks in advance for your help!

@AminTi
Copy link
Collaborator

AminTi commented Aug 22, 2023

Thanks for reporting. We'll dig into this.

@chtjfi
Copy link
Author

chtjfi commented Aug 29, 2023

Thanks for your reply! Did you have a chance to look into it yet?

@TadeuTorres
Copy link

TadeuTorres commented Nov 9, 2023

We have the same problem. Removing the extension and adding it again, also didn't solve the problem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants