Paket Restore task not authenticating to VSTS about vsts-fsharp

[jason-gill]

Turns out that adding CredentialProvider.VSS.exe to our build script had unintended consequences.

I changed our build script to copy the CredentialProvider.VSS.exe to the %LocalAppData%\NuGet\CredentialProviders directory which is the first directory Paket looks in for credentialing providers. In an AWS environment that provider doesn’t work because you need an access token to authenticate to VSTS. Because that credentialing provider was the first one found, Paket would hang trying to authenticate itself. Once that provider was removed, then Paket restore was able to find the credentialing provider installed by the “Setup Paket Credential Manager” task and everything works like it should.

[matthid]

Thanks a lot for this analysis, does that mean the first provider was trying to get interactive input from the user? Maybe we can improve that scenario by printing a warning in paket after a while when the credentials provider doesn't exit?

[jason-gill]

Yes, I do think that is what happens. I remember during my testing running the build manually on one of the build boxes and I got a login popup. After putting in my credentials that build box never had the authentication problem again but the other build boxes did.