This table clarifies how to specify the configuration file values: Entry: If the file does not already exist, create an empty text file.įormat your authentication information using a schema, depending on whether you are using a Bearer (token-based) or Basic (Base64-encrypted) authentication mechanism: Once you save this information to the configuration file, Package Manager will provide your authentication information on every request made to each registry in the file.įollow these instructions to add your authentication information to the user configuration file: upmconfig.toml user configuration file using the npmAuth configuration schema. Store your token information for each scoped registry that requires authentication in the. npmrc file containing an _auth attribute: registry= npmrc file containing an _authToken attribute: registry= Locate either the _authToken or the _auth entry and copy its value (see the example below).ĭepending on the registry, the token string can be either a GUID, a token, or a proprietary-formatted string. To fetch an authentication token from npm:įrom a terminal, enter this command to log into the registry: This is an example of a typical procedure, but you need to follow the process recommended by the specific package registry provider for your scoped registry.
For example, JFrog’s Bintray and Artifactory repository managers use a different procedure to generate the authentication token from npm. The process of creating and accessing an npm authentication token is different for each registry provider. To set this up, get an npm authentication token and then add that token to your user configuration file. If you are an employee or customer of one of those organizations, you must configure a scoped registry with npm authentication. Some organizations host their own packages on private package registries that require authentication to access.
0 kommentar(er)
