Authorization Request:

[kristow]

Describe the bug
When navigating to the @scale extension in the Boards feature of Azure DevOps Server, the user is prompted to "Sign in to access this site".

To Reproduce
Steps to reproduce the behavior:

1. Go to internal AzureDevOps Server collection.
2. Click on the project
3. Select the "@scale" extension option under "Boards" feature
4. The Windows Security prompt to "Sign in to access this site pops up multiple times. This only occurs when accessing @scale.

Expected behavior
Access to ADO for our on-premises server uses windows authentication. There should be no prompts for authorization when accessing @scale extensions.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Browser: Edge
• Version: 106.0.1370.47

Additional context
Add any other context about the problem here.

[JimmyKB]

Hello @kristow. Thank you for reporting this to us.

Could you tell me if you are using and if you have linked work items in the board to Azure DevOps Testplans/test cases?

We think that this issue has to do with Microsofts APIs on-prem when visualising work items that have links to Test plans/test cases that users don't have access to.

[kristow]

Hi @JimmyKB. Yes, there are features on the board that have children product backlog items that have linked test cases.

[JimmyKB]

Thank you for informing @kristow
We're investigating the issue, and I will close it once we have a solution.

Kind regards

[kristow]

Hi @JimmyKB, any update or ETA on a solution to this issue?

[JimmyKB]

We have been able to reproduce the issue however we've not been able to solve the issue at this moment. We're aiming for a solution next week. It has to do with MS APIs.

[kristow]

Hi @JimmyKB any update?

[JimmyKB]

Hello @kristow, It looks like it's an API issue, we have reported it to MS and are waiting for the response. I'm sorry for the inconvenience but seems to be out of our control. I'll remind them once again and I'll close this issue as soon as it's resolved.

[JimmyKB]

@kristow Has this issue been resolved yet? What version of Azure DevOps server are you running on and when did you have your last update?

Kind regards