Authenticate is called for every package install
See original GitHub issueWhen a package is not scoped we don’t need to call authenticate all the time. We DDOSed our private GitLab instance when anyone installed a lot of packages, because GitLab was requested several times even if the package asked for was not scoped and available on public npm.
Request pile up very quickly when installing express
for example. It makes a request for every package used by express
.
Issue Analytics
- State:
- Created 6 years ago
- Comments:29 (7 by maintainers)
Top Results From Across the Web
Authentication Packages - Win32 apps | Microsoft Learn
Security protocols are implemented by authentication packages. An authentication package analyzes logon data by following the rules and ...
Read more >Authentication for privately hosted packages and repositories
Whenever Composer encounters a protected Composer repository it will try to authenticate using already defined credentials first. When none of those credentials ...
Read more >Working with the npm registry - GitHub Docs
Authenticating to GitHub Packages. Publishing a package. Publishing multiple packages to the same repository. Installing a package. You can configure npm to ...
Read more >npm install gives unauthorized name or password is incorrect ...
Go to your this location C:\Users\{your user name or ID} 2.> open .npmrc & Remove all content from .npmrc file. 3.>reopen your new...
Read more >polkit - ArchWiki
The polkit package contains a textual authentication agent called ... graphical authentication agent is installed and autostarted on login.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
We set up verdaccio for private modules. We want to use the features of npm and not install our (proprietary) modules from GitLab or publish them on npm (registry.npmjs.org)…
Would be great to use GitLab as authentication provider, because we already use it. Caching the groups would be it. Group owners are not changing very frequently… Do you have any idea how that could be achieved?
Just FYI, I’m working on an implementation using node-cache as suggested by @bufferoverflow. It’s not a perfect solution, but a small, manageable implementation. By comments of the maintainer in verdaccio/verdaccio/issues/732, I don’t think support for it will be added in the parent project.