[INFO REQ] NPM auth details in .npmrc

[sfry]

Hi

Thanks for this help.

The local (or global) .npmrc will contain the Artifactory credentials only. We expect the credentials for Bryntum to be hidden from the developers or CI processes completely (by Artifactory). As far as they are concerned the packages are coming from Artifactory.

An Artifactory virtual repository will try all of the local and remotes within it in the order specified in order to find a requested artifact.

Nothing special is needed in the project, in fact most of our projects do not have a .npmrc as we rely on the development environment or build environment to have a user level one.

So your package.json entry would be exactly what we would expect.

Thanks again

Stephen

[sergey.maltsev]

Hi!

Thank you for this info.
This is the related issue https://github.com/bryntum/support/issues/2864
We are working on this problem.

[sergey.maltsev]

Hi!

We've updated server to support username/password auth for Artifactory.
Tokens are yet not supported due to some issues from Artifactory side.

Could you please check if this instruction valid for serving packages.
These docs will be available online after update.
You might know of this already but this is here for someone who may search for the solution.

To use Bryntum NPM registry as a remote repository please follow this instruction.

Add Bryntum registry as a remote repository

In Artifactory admin console navigate to Administration - Repositories and click Add repositories - Remote
repository.

Check Remote Repositories docs from Artifactory.

Configure repository with:

Parameter	Value
Package Type	npm
Repository Key	bryntum (or any other name you prefer)
URL	https://npm.bryntum.com
Username	Username for Bryntum repository authentication
Password	Password for Bryntum repository authentication

Setup credentials for @bryntum package access

After creating remote repository click on wrench icon (Set Me Up) in the line with the repository to get credentials for
accessing repository.

Create .npmrc file in the project's folder and add credentials there for @bryntum scope packages:
For example if you use JFrog Platform for hosting your Artifactory registry (e.g. yourregistry.jfrog.io) for
Artifactory with the user name user@example.com than you will have similar config:

@bryntum:registry=https://yourregistry.jfrog.io/artifactory/api/npm/bryntum/
//yourregistry.jfrog.io/artifactory/api/npm/bryntum/:_password=<BASE64_PASSWORD>
//yourregistry.jfrog.io/artifactory/api/npm/bryntum/:username=user@example.com
//yourregistry.jfrog.io/artifactory/api/npm/bryntum/:email=user@example.com
//yourregistry.jfrog.io/artifactory/api/npm/bryntum/:always-auth=true

<BASE64_PASSWORD> will be generated for you in Artifactory console if you enter your credentials there.

After these actions you will be able to install @bryntum packages with your Artifactory login from .npmrc file.

Later you may add bryntum Artifactory remote repository to any virtual repository to have access to several
repositories with the same Artifactory credentials.

Check Virtual Repositories docs from Artifactory.

Note Artifactory may serve cached packages so it would be better if you recreate remote repository and may be with different name.

Please let us know if this helps.