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

Problems consuming packages from Azure DevOps when authenticating with PATs #741

Closed
nblumhardt opened this issue Nov 5, 2018 · 13 comments

Comments

@nblumhardt
Copy link
Member

commented Nov 5, 2018

Via: https://docs.getseq.net/v4.2/discuss/5bda8ea05fa411001312a778

We need to investigate/provide guidance on how to authenticate against VSTS feeds when installing app packages.

@nblumhardt nblumhardt added the bug label Nov 11, 2018

@nblumhardt nblumhardt added investigation and removed bug labels Nov 19, 2018

@nblumhardt

This comment has been minimized.

Copy link
Member Author

commented Apr 23, 2019

It appears we should be able to authenticate using a random username, with a PAT as the password.

Is anyone doing this successfully with Azure DevOps?

@nblumhardt nblumhardt changed the title Problems consuming packages from VSTS when authenticating with PATs Problems consuming packages from Azure DevOps when authenticating with PATs Apr 23, 2019

@madacrobat

This comment has been minimized.

Copy link

commented May 23, 2019

I'm afraid the PAT solution isn't working to vsts. Still getting 401 but after a much longer delay (about 15 seconds). Haven't looked at the vsts logs but suspect they won't have anything interesting in them. I've created a local nuget feed on the seq server for now but this will be bit of an issue for us.

@nblumhardt

This comment has been minimized.

Copy link
Member Author

commented May 23, 2019

Thanks for the feedback @madacrobat .

I'll pop this into our next patch milestone and try to make some progress on it 👍

@nblumhardt nblumhardt added this to the 5.1-patch4 milestone May 23, 2019

@nblumhardt

This comment has been minimized.

Copy link
Member Author

commented Jun 7, 2019

We have some changes coming in the next patch (ideally next week) that improve our chances of succeeding with this. Instead of constructing URLs within the client, we stick more carefully to the the NuGet V3 protocol's hypermedia structure, and hopefully avoid touching any inaccessible URLs in the process.

It'll be necessary to use a v3 feed endpoint for VSTS (on both Windows and Linux), random username, PAT as password.

With a large dose of optimism, I'll close this, and re-open if the issue is reproducible in the new version.

@nblumhardt nblumhardt closed this Jun 7, 2019

@nblumhardt nblumhardt added bug and removed investigation labels Jun 7, 2019

@nblumhardt

This comment has been minimized.

Copy link
Member Author

commented Jun 9, 2019

This has shipped in 5.1.3118

@madacrobat

This comment has been minimized.

Copy link

commented Jun 10, 2019

Looks like this is still failing with 401 using local TFS. V3 feed (ends with ..../nuget/v3/index.json), random username and PAT as password. This feed works fine in VS 2019 (and earlier). Sorry!

@nblumhardt

This comment has been minimized.

Copy link
Member Author

commented Jun 10, 2019

Aw, snap! Thanks @madacrobat - reopening, will have to take another look.

@nblumhardt nblumhardt reopened this Jun 10, 2019

@nblumhardt nblumhardt modified the milestones: 5.1.3118, 5.1-patch5 Jun 10, 2019

@nblumhardt

This comment has been minimized.

Copy link
Member Author

commented Jun 11, 2019

Having another try; is anyone following this able to test out a pre-release build?

@madacrobat

This comment has been minimized.

Copy link

commented Jun 12, 2019

Sorry, I should have replied yesterday. I'll try pre-release when you have it. BTW @nblumhardt, this is Ian from Skogsstyrelsen using my personal GutHub account because I'm too lazy to logout and in again :-)

@nblumhardt

This comment has been minimized.

Copy link
Member Author

commented Jun 13, 2019

Sent! Thanks @madacrobat 👍

@madacrobat

This comment has been minimized.

Copy link

commented Jun 13, 2019

Hi @nblumhardt but the same result (401) with the pre-release. Just a thought but when I create the PAT in TFS it says I need to use the generated token as the password rather than PAT as you suggested. Is that perhaps a clue to the problem? The problem with nuget access via TFS isn't on my critical list so whilst it would definitely be nice to have working I can live with a local nuget repository for now (I only have 1 app anyway at the moment).

@nblumhardt

This comment has been minimized.

Copy link
Member Author

commented Jun 13, 2019

Argh - :-) ... thanks @madacrobat. We'll figure it out from here.

@nblumhardt

This comment has been minimized.

Copy link
Member Author

commented Aug 26, 2019

Fixed in 5.1.3190

@nblumhardt nblumhardt closed this Aug 26, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants
You can’t perform that action at this time.