Closed Haard30 closed 1 year ago
NUGET_CREDENTIALPROVIDER_MSAL_FILECACHE_LOCATION
is expecting a directory and will use msal.cache as the file name, so if that environment variable points to an already existing file then you'll get this error. I need to check the history to see if these semantics have changed between token caches between ADAL and MSAL, but as far as I know the MSAL cache behavior (expecting a directory path) have not changed.
Looks like behavior has changed from previous versions, and specifying the full file path was supported.
Published 1.0.9 (not as latest), can you install the new version to see if it resolves your issue?
iex "& { $(irm https://aka.ms/install-artifacts-credprovider.ps1) } -AddNetfx -Version 1.0.9 -Force"
Published 1.0.9 (not as latest), can you install the new version to see if it resolves your issue?
iex "& { $(irm https://aka.ms/install-artifacts-credprovider.ps1) } -AddNetfx -Version 1.0.9 -Force"
The fix is working and we no longer get that error with 1.0.9
. Thank you so much John for looking into this. Really appreciate it! 😃
Description
Using artifacts-credprovider v1.0.8 as credential provider for Nuget 6.2.1.2, we routinely encounter following problem when running
nuget restore
.We had a brief look at the artifacts-credprovider code and wondered if the
SessionTokenCache
might be conflicting with MSAL but we are not experts in this codebase and weren't able to debug it further. This seems like an unexpected behavior but in case we are wrong, we have provided full stack trace after redacting internal information.Command
Environment variables
Nuget output and Stack Trace