Added support for On-PREM Azure DevOps #251
Conversation
|
@Axecalever AZURE_DEVOPS_AUTH_METHOD=pat |
|
I am using it with a PAT token generated for an admin account.
Try running Postman using following config:
Endpoint: https://si0vmc3960.de.vic.com/tfs/DefaultCollection/<project->/_apis/release/definitions/149?api-version=7.1
Body:{"Id": <id of one of your build pipeline>}
Authorization: use the PAT generated in password (no username required)
…On Tue, Aug 12, 2025 at 2:36 PM SonRobo ***@***.***> wrote:
*SonRobo* left a comment (Tiberriver256/mcp-server-azure-devops#251)
<#251 (comment)>
@Axecalever <https://github.com/Axecalever>
I applied your changes, but when I use the getme tool, it returns an
"unauthenticated" error.
AzureDevOpsAuthenticationError: Failed to connect to Azure DevOps: Failed
to authenticate with Azure DevOps: unable to get local issuer certificate
Here are the environment variables I set:
AZURE_DEVOPS_AUTH_METHOD=pat
AZURE_DEVOPS_ORG_URL=https://si0vmc3960.de.vic.com/tfs/DefaultCollection
AZURE_DEVOPS_PAT=
Also, could you provide me with the API details so I can test it using
Postman?
for example https://si0vmc3960.de.vic.com/tfs/_apis/ConnectionData with
bearer token right?
—
Reply to this email directly, view it on GitHub
<#251 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABHQCWMXO2F7QVWFR5BKTGT3NGYS7AVCNFSM6AAAAACDDSVYPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTCNZYGU2TINBWGI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Code ReviewGood: Adds pattern matching for on-premise Azure DevOps Server. Issue: Incomplete implementation. Only fixes organization name extraction but doesn't address:
Needs:
This PR is a start but needs significant additional work for full on-prem support. |
As I am using on-prem deployed azure devops server. I believe this patch will be able to take URLS others than "dev.azure.com"