Azure devops nuget feeds
Comments
-
Point 1 can easily be fixed, but point 2 creates much more of a problem. The only viable workaround would be to retrieve every package and then filter locally. Would this work in your case? I don't know whether the search API also flows through to an upstream source. If so, this would definitely not be a solution.
-
Thank you for your reply, Joe. LINQPad is a great product.
If space can be removed, one can rename their package and put 'LINQPadDriver' (case insensitive) in package name and this package will be returned by DevOps feed. That was my personal plan. Looks like they do not search by tag values, nor do they search by description. Another alternative will be to publish the package in a different NuGet feed implementation (e.g. nuget.org), but that is not currently possible. Azure DevOps Authentication works fine though.
If upstream sources are used, DevOps passes query to them and they DO support searching by tags or/and trim the space at the end.
-
OK - will remove the trailing space for the next build. Search will still not work (because there will be space in the middle) but you'll at least be able to list all packages with linqpaddriver in the package name.
-
I'm not sure what I'm doing wrong. I'm on LINQPad 9 Premium v9.8.12. I've done a nuget source basic auth, username ID, and PAT for the password.
I'm using http toolkit to see what linqpad is doing, and I'm using an http url so I can see traffic. It doesn't send basic auth. The only headers are these.
Why is it not sending basic auth?
-
Does the server first respond with a 401/403?
And if so, does the 401 response include WWW-Authenticate: Basic realm="..."?
And is there a retry request? The "Authorization: Basic" header only appears on the retry after the 401.
-
Yes. It tries 4 or 5 times, and everytime the response from the server has these headers in it. The request never sends basic auth.
-
Does it match the URI entered in Settings exactly?
-
It's matching the web app in IIS.
Here are the URls and screenshots without any redaction.
http toolkit
Rider, and Visual Studio pull nuget packages via Kerberos. I've never been able to get that to work in LINQPad after version 5, each new version of LINQPad that left the old 4 framework I've tried to get the packages to work with on premis Azure DevOps but haven't been able to.
I did a program to test out the PAT auth with the httpclient and it worked, so I decided to focus on seeing if I could get linqpad to work with PAT.
-
Ah, now I see the problem. The %20 sequences will get converted to spaces when parsed into a URI and then it will never find the right credentials provider.
I've just uploaded v9.9.10 - please let me know whether it fixes it:
https://www.linqpad.net/linqpad8.aspx#betaIf it works, can you also try Windows authentication and let me know whether that now works, too.
-
Yes the PAT authentication works now!
For Windows Auth it does not seem to work. I did Windows Auth, and entered my username/password. I could not see any change in the http traffic. I also tried System Default credentials and that didn't work either. I didn't see the kerberos ticket passed.
I really appreciate you doing the alteration. I've used LINQPad a very long time, maybe near the start, it's what enabled me to learn dotnet really well almost 20 years ago. I had come up with a workaround to download packages locally and sync them, but this will be so much better. Thanks!
