nexus - Unable to publish to an NPM Registry (local) -
i running nexus 3.0.1-01, , using host both maven repositories , npm registries. npm, have local mirror of npmjs.org, local npm registry , group combines two...
i have been using npm internally, can use npm-public group registry , has been working fine. so, can use nexus mirror npmjs.
the next step take locally written npm modules , publish them npm-releases (on nexus instance) these modules can shared amongst delivery teams here. i've been able build out package, , npm pack seems behave.
i have run npm adduser provide nexus credentials npm environment. using same username/password use when log nexus web app, , user assigned admin role (so should have permissions). can see credentials in .npmrc file
my registry value still npm-public group combined mirror , local registry. have ensured package.json of module attempting deploy has "publishconfig" section points url of local registry (not public group)
however, despite of that, calling "npm publish" results in 401 error...
looking @ npm-debug.log, can see it's attempting call http put call push assembled tgz file registry, , returning 401 error
i have enabled debug logging on shiro package in server, ever see single message thinking needs authentication
2016-09-13 08:56:28,590+1000 debug [qtp1257823896-4030] *unknown org.apache.shiro.web.filter.authc.basichttpauthenticationfilter - authentication required: sending 401 authentication challenge response.
according documentation, i've done i'm supposed (npm add user) unable deploy npm module local repository.
are there additional options need use when calling npm publish? there additional settings need make hosted npm repository in server allow me publish it? pretty created using default values. have missed step preventing me deploying hosted npm registry?
any appreciated, stuck @ moment.
as turns out, did not have npm bearer token realm in list of active realms. once moved active, publish completed successfully!
Comments
Post a Comment