Publish npm package to Proget

[Guest]

Hi, Jason!
Thanks for your reply.
I need to login automatically (from CI, TeamCity)
So, when i'm trying use npm login, its asking user and password

[jjones]

This seems to be a known limitation for automating a publish command. Some recommend using npm-cli-login in order to provide login credentials.

Thanks,
Jason

[Guest]

And there are no way to publish npm packages with tokens and without any additional plugins?

[jjones]

Here is what we have documented for publishing npm packages to proget from a command line..

To configure npm to use the npm ProGet feed, run the following command:

npm config set [@scope]:registry http://progetaddress/npm/npm
If your feed does not allow anonymous access, you will also need to run this command:

npm config set always-auth true [--scope:@scope]
To log in to ProGet using npm, run the adduser command and specify a ProGet user account and password:

npm adduser --registry=http://progetaddress/npm/npm [--scope:@scope]

These commands will need to run before trying the publish command. Once this configuration is set up, it shouldn't be required again. But that would need to be confirmed on your end.

[Guest]

Yes, I read documentation already.
When I try to login, i've got an error:
Username: (api)
Password: (<default hidden>)
Email: (this IS public) MyEmail@mycompany.com
npm ERR! code E403
npm ERR! Registry returned 403 for PUT on https://MyProgetServerl/npm/-/user/org.couchdb.user:api

npm ERR! A complete log of this run can be found in:
npm ERR! C:\Users\user\AppData\Roaming\npm-cache_logs\2019-05-23T09_27_00_415Z-debug.log

[jjones]

run:
npm config get registry

if you don't see the correct registry

try:
npm config set regist <urltoregistry>

[Guest]

npm registry configured properly

I'm trying to do this:
npm Token Authentication
In order to interact with your private registry without using the npm adduser command you will need to follow these steps:

Create an API Key - you can create an API Key in ProGet (Admin > API Key & Access Logs) with Feed Access. you can further restrict this key by associating it to a user you've already given specific permissions
Encode The API Key - Once the key has been generated you will need to encrypt the key along with the username api. This needs to be encoded in base64 format. Your string prior to encoding should be: api:{APIKEY}
Once you have this token you will need set your _auth value with it using npm. It is also recommended that you set always-auth to true.

[~]$ npm config set always-auth=true
[~]$ npm config set _auth={ENCODEDAPIKEY}

https://inedo.com/support/documentation/proget/feeds/npm

Does it works in proget ? or I cant login with auth token?

[jjones]

Hi Taras,

This has been tested in ProGet, in order to publish with Token authentication:

• You need to create a user in proget
• give that user the Add Package role
• create a new token that impersonates that user.
• encrypt the token to base64

[Guest]

Hi!
Som i've genereate a token like this : FHGDSFREG-3FrF
Then, accroding to documentation, i need to encrypt this key with user API
Before encryption should be like this:
api:{FHGDSFREG-3FrF}
after encryption with base 64 will be string: YXBpOntGSEdEU0ZSRUctM0ZyRn0g
Then, I need to add this with command:
npm config set _auth={YXBpOntGSEdEU0ZSRUctM0ZyRn0g}
Correct?

[Guest]

Hi! Any updates ?

[jjones]

Taras,

try encrypting without the brackets {}

so encrypt this first:

api:FHGDSFREG-3FrF

your command should exclude {} as well

npm config set _auth=YXBpOntGSEdEU0ZSRUctM0ZyRn0g__newtoken

[shihui0304_6759]

hello, any updates?
I also encounter the same problem. How can I fix it?

[pcoombe_0297]

looks like ive found my way here as well, the documentation isnt very clear to include or not include the {}s
ive tried both, and cant get it working either (i can publish with username and password but not api key)

@jjones said in Publish npm package to Proget:

__newtoken

Can you explain why this is on the end of your command?

i also see various things that scoped packages should be using _authtoken not just _auth, my package is scoped

[ben]

Hello @pcoombe_0297,

You can use api as the username and an API key as the password for any feed API supported by ProGet.

The auth format is HTTP Basic auth, so you'd prefix the API key with api: and then base64-encode the result.

You can also log in interactively via the npm login command. If your ProGet username cannot be used as an NPM username (such as a qualified domain user), ProGet will also accept the username via the email field.

[pavlok_7223]

Any updates on this? I encounter the same issue and none of your comments helped
.