Credential Providers intermittently prompts for credentials
Nobody has claimed this yet.
- Dominant language
- F#
- Stars
- 2.1k
- Forks
- 528
- Avg merge
- 1d 12m
- Merged PRs (30d)
- 54
Description
Description
Following the description at the documentation page I have set up our Azure DevOps build agents, i.e.
- Extract the CredentialProvider.VSS.exe file into the above path (%LOCALAPPDATA%\NuGet\CredentialProviders)
- Run
CredentialProvider.VSS.exe -U NUGET_FEED_URL
Then enter user name and password.
This seems to work for a few weeks (unsure of the time period, maybe 4-8 weeks) and then the build process starts asking for credentials again, there by blocking builds on our agents.
Repro steps
Unfortunately there are no specific steps to reproduce this issue. Maybe someone can confirm if the steps I have taken to setup the Credential Provider are correct?
Expected behavior
I would expect, once the Credential Provider is setup, paket resolves credential and doesn't forget it after a few weeks to have to re-enter password on every single build agent.
Actual behavior
Paket forgets the credentials and build fails with the following log:
Paket version 5.215.0
Resolving packages for group Main:
Performance:
- Resolver: 7 seconds (1 runs)
- Runtime: 107 milliseconds
- Blocked (retrieving package versions): 7 seconds (1 times)
- Runtime: 8 seconds
Paket failed with
-> Unable to retrieve package versions for 'EWSoftware.SHFB'
-- CLOSED --
-- OPEN ----
EWSoftware.SHFB == 2017.12.30.2
Known workarounds
I do not know of a proper workaround. I go on every single build agent to re-configure the Credential Provider as explained in the Description section.
Once re-configured, paket works as expected for few more weeks.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the credential-provider documentation and the CredentialProvider.VSS.exe setup command described in the issue, then reproduce the configuration on an Azure DevOps build agent if possible. Investigate why Paket or the provider stops resolving credentials after several weeks; done means builds continue without prompting after the documented setup, with regression coverage or documented reproduction steps.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- devops, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100