Cannot log in with npm #24
Comments
|
Hey, are u sure u are running 2.0.1? We faced the same issue and introduced #23 as a fix. It works for us now, doesn’t it @tobilarscheid? |
|
Yes, 2.0.1 was fixing exactly that. |
|
@stephenmuss did you do any special config for docker? How do you access your registry? |
|
@schmitzhermes @tobilarscheid yes, my bad. My ansible playbooks were telling me 2.0.1 but when I logged into the server it was still using 2.0.0. Had better run those playbooks! Sorry for the red herring and thanks for your hard work! @elntagka no special config apart from having to run the docker registry on a separate port as per the docs. |
|
@stephenmuss would you mind publishing the relevant ansible code? I would like to link to it from the installation instructions! |
|
@tobilarscheid I'll see if I can find some time to publish a role to Ansible Galaxy. Cheers. |
|
@stephenmuss sorry to bother you again, but does |
|
@tobilarscheid no, I have still been having problems with npm. Npm login works but npm install is getting 401s. I didn’t find too much helpful in the logs. I had to create local accounts as a temporary work around. |
|
Yes, exactly my issue! Really strange, it works flawlessly with local accounts - so I think there must be something to change on the plugin... |
|
Let me know if I can help test anything. |
|
I am clueless at the moment, let's see if the sonatype guys have an idea: https://issues.sonatype.org/browse/NEXUS-16727 |
|
@tobilarscheid I have the 401 issue as well and just went through the nexus ticket you raised. Thanks for pushing sonatype guys to find the solution. Really hope this issue could be addressed soon. |
|
Hi @lqin-pki sorry to hear that. I know its pretty annoying and limiting the usefulness of this plugin... Unfortunately I don't have the time to dig deeper into nexus and understand whats the underlying problem. If you have any ideas, feel free to post here or over in nexus jira! |
|
@stephenmuss @lqin-pki the nexus guys just closed the issue (NEXUS-16727) I opened - saying that the problem appears to be outside of the NXRM product. I can not say if this is true or not, nor can I invest much time at the moment to dig deeper into it - maybe one of you guys can take over. |
|
I'll see what I can dig up when I find some time. |
|
Hi @stephenmuss @lqin-pki any news on this? |
|
I haven't looked at it tbh. We're using local accounts for npm to work around the issue. |
|
Thanks for your feedback. Did anyone manage to test that with nexus |
|
I setup a "Sonatype Nexus Repository Manager OSS 3.16.1-02" with plugin 2.0.2 |
|
Hi Christoph, thanks for your feedback. To me it still looks like a general problem with nexus or a general problem with how we implemented this plugin. Anything you can reverse engineer helps! Regards, Tobi |
|
Hello, As a workaround, configure your login with: Note that the above workaround is bypassing the secure indirection of Nexus local tokens. |
|
Wow, thanks for your detailed analysis - I just learned a lot about the combination of nexus and npm by reading through your tickets. So apparently there is some special (but not well documented) voodoo required when writing a custom authentication that is supposed to play nicely with npm. Happily waiting for your PR ;-) |
|
Hello, The custom .npmrc looks like the following: I wasn't able to do an npm login because all the usernames being used in Github are in capital letters, so this was our approach. |
I am getting a 500 response from Nexus when attempting to log in using npm.
I am able to log into the Nexus web UI and also docker with my Github credentials, but npm doesn't seem to work.
I'm running Nexus Repository Manager Pro 3.9.0-01 and nexus3-github-oauth-plugin 2.0.1.
I've provided both the npm debug log and logs from the log viewer in the Nexus UI.
.npm/_logs/2018-03-26T02_51_03_568Z-debug.log
Nexus Server Log
The text was updated successfully, but these errors were encountered: