Unable to authenticate, need: Basic realm="GitHub" about alks-cli HOT 9 CLOSED

Count me in on this issue. By switching to always-auth=false in .npmrc, I got past it. Would be nice to not have to remember to do that every time I upgrade alks. BTW - This is my personal GH account. If necessary, you can find me at eric.hall in Cox Auto land.

from alks-cli.

@aaron-seitz no, per my PR this is an issue with using always-auth=true (required for private registries that need auth on GETs) and having a generic URL as a dependency. If you use the shorthand for GitHub URLs, installs work perfectly.

If a GitHub dependency of the form Cox-Automotive/clortho#1.2.3 is causing issues with the build system, you can try using git+https://github.com/Cox-Automotive/clortho#1.2.3 to force downloading with https. Either way is perfectly valid syntax, and the build system should support it.

This has prevented us from updating alks-cli past version 3.0.5.

Edit: Note that per the NPM documentation link above, https://github.com/Cox-Automotive/clortho/archive/1.2.3.tar.gz is not a valid GitHub dependency format.

from alks-cli.

I'm running in to this issue as well. My naive assumption is that one could setup a custom registry and then npm would check that first and the standard registry if the package is not foundf. Certainly there must be a solution to allow for both custom and default registry that isn't "swap your .npmrc whenever you use npm"?

from alks-cli.

so I have the same issue. Reading into node docs I suggest creating different profiles and using npmrc to swap between company and public profiles. https://docs.npmjs.com/configuring-your-registry-settings-as-an-npm-enterprise-user

from alks-cli.

Hello! Looking into the issue, we believe this is actually a misconfigured custom npm registry (setup such that it doesn't know how to properly resolve GitHub links). Can you check and verify if this is the case?

from alks-cli.

I am trying to install the alks-cli on node v13.12.0 (nodejs stable), I am also getting the error message

Unable to authenticate, need: Basic realm="GitHub"

Is the alks-cli not compatible with node 13??

from alks-cli.

@rsturim we've also seen this issue recently, specifically here, where the issue ended up being that there are more than 1 alks instances found. Using the command which alks to find if there are more than one can help resolve this issue.

from alks-cli.

I'm experiencing the same issue with a different repo and it is rather frustrating to swap npmrc files. There needs to be a better way of doing this.

from alks-cli.

This issue should be resolved for all users in versions 3.2.5 and up now that PR #191 has been deployed since we're no longer using github URLs for the clortho dependency. Please open another issue if any other issues occur as a result of this change

from alks-cli.