Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NPM private feed. What is correct url format? #6411

Closed
JonnyMattsson opened this issue Feb 12, 2018 · 3 comments
Closed

NPM private feed. What is correct url format? #6411

JonnyMattsson opened this issue Feb 12, 2018 · 3 comments
Assignees

Comments

@JonnyMattsson
Copy link

JonnyMattsson commented Feb 12, 2018

Troubleshooting

Environment

VSTS

Issue Description

We have a private feed that is accessible from "https://ourproject.myget.org/F/subcategory/auth/abc123.....456/npm/"

What is the correct format for the url in the npm service endpoint configuration and the .npmrc file?
It works fine if I have the full path including the token in both urls. But I would like to have the .npmrc file without any token. I have tried with "https://ourproject.myget.org/F/subcategory" and "https://ourproject.myget.org/F/subcategory/npm" but the npm task fails due to unauthorization.
The token should be taken from the npm service endpoint, right?

@infin8x
Copy link

infin8x commented Feb 14, 2018

@JonnyMattsson You can get the feed URL from https://www.myget.org/feed/Details/[your feed], I believe. Should look roughly like https://www.myget.org/F/amullans/npm/.

Put that exact URL both in your .npmrc and in the npm Service Endpoint (https://[your account].visualstudio.com/[your project]/_admin/_services?_a=resources).

@JonnyMattsson
Copy link
Author

@alexmullans I tried that but it didnt work.
I have attached two outputs. One with the format you suggested and one where the token is included in the .npmrc file.

Suggested format:
npmwithoutauth.txt

With token
npmwithauth.txt

keithrob added a commit that referenced this issue Feb 19, 2018
@keithrob
Copy link
Contributor

This will be fixed by this PR. In the meantime you should be able to use basic auth in a service endpoint with myget.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants