4.x displays Anonymous even if publisher is authenticated
See original GitHub issueDescribe the bug
Publishing displays Anonymous user.
To Reproduce As an authenticated user, publishing a package under verdaccio v4-next displays Anonymous as uploader.
Expected behavior As a logged user, the user who published the package should be displayed properly
Screenshots
Docker || Kubernetes (please complete the following information):
- Docker verdaccio tag: [e.g. verdaccio:beta] verdaccio:4.x-next
- Docker version: 17.03.2 (through kubernetes)
Command: just running the image with config mounted at proper place.
Configuration File (cat ~/.config/verdaccio/config.yaml)
storage: /verdaccio/storage/data
plugins: /verdaccio/plugins
uplinks:
npmjs:
url: https://registry.npmjs.org/
packages:
'@*/*':
access: $authenticated
publish: $authenticated
proxy: npmjs
'**':
access: $authenticated
publish: $authenticated
proxy: npmjs
web:
enable: true
title: OurCompany
scope:
logs:
- {type: stdout, format: pretty-timestamped, level: http}
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Anonymous Authentication - an overview
Select Anonymous Authentication from the new screen on the right. 4. From the “Actions” menu on the far right, select disable (this can...
Read more >Prevent authentication prompt for anonymous
If the user wants to access the relevant page, I suggest you give relevant permission to a user account and login with this...
Read more >FTP Anonymous Authentication <anonymousAuthentication>
This form of authentication allows access to an FTP site without a user account on your server or domain, and is most often...
Read more >How to Enable Anonymous Access in SharePoint 2013 ...
Enable anonymous access for SharePoint 2013 web application: ... Click on the relevant zone from the authentication providers. In my case, it's “ ......
Read more >Windows Built-in Users, Default Groups and Special ...
Default Group Special Identity Description
Cert Requesters Members can request certificates (Domain Local)
Digest Authentication Default User Rights: None
NTLM Authentication Default User Rights: None
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 Free
Top 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

Yes and it has the same name and email than the npm registry account
@blackholegalaxy After analyzing the problem, the conclusion is: NPM parses and converts the author property of package.json to an object before sending it to the registry. if the author is not there, we will display the author as Anonymous. Could you share the version of your NPM / YARN or the name and version of your package manager? So we can try to better simulate your problem. And please share your package.json…Thank you!