dosubot[bot] commented on issue #7535:
URL: 
https://github.com/apache/incubator-devlake/issues/7535#issuecomment-2136575469

   <!-- Answer -->
   The "Unauthorized request" error you're encountering might be due to a known 
issue in the AzureDevOpsPlugin version v1.0.beta. This issue occurs when Azure 
DevOps returns a status code of 203, which indicates an invalid token and 
resolves to a sign-in page. The plugin changes this status to 401 and raises an 
exception, leading to the "Unauthorized request" error 
<sup>[[1]](https://github.com/apache/incubator-devlake/blob/main/backend/python/plugins/azuredevops/azuredevops/api.py)</sup><sup>[[2]](https://github.com/apache/incubator-devlake/blob/main/backend/plugins/azuredevops_go/api/azuredevops/client.go)</sup>.
   
   To further diagnose the issue, you can enable logging within the plugin to 
get more detailed information about why certain projects are failing to load. 
The `PrepareTaskData` function in the `impl.go` file uses a logger to log 
various informational messages and errors, which can help in debugging 
<sup>[[3]](https://github.com/apache/incubator-devlake/blob/main/backend/plugins/azuredevops_go/impl/impl.go)</sup>.
   
   Ensure that your PAT has 'Full access' and is set to 'All accessible 
organizations'. If the issue persists, consider checking the specific scopes 
and permissions required for the operations you are attempting.
   
   
   <!-- Dosu Comment Footer -->
   <details>
   <summary>
   
   #### Details
   </summary>
   
   **About Dosu**
   This response is meant to be useful and save you time. It is **not meant to 
be a precise solution**, but rather a starting point for your own research.
   
   Help me be more useful! Please leave a 👍 if this is helpful and 👎 if it is 
irrelevant.
   </details>
   
   *To continue the conversation, mention @dosu.*
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to