![]() Under Select organizations, select the organizations you want to grant your token access to.(Optional) In the Organizations section, configure your token's access to organizations. Then select specific packages or scopes from the dropdown menu. Only select packages and scopes to choose up to 50 specific packages or scopes to give the token access to.All Packages to grant the token access to all packages the user account has access to.In the Permissions dropdown menu, select No access, Read-only, or Read and write.(Optional) In the Packages and scopes section, configure your token's access to packages and scopes. To add more than one allowed IP range, click Add IP Range and enter an IP range in the new text field. You must use CIDR notation to enter IP address ranges. (Optional) In the Allowed IP Ranges field, enter IP address ranges to restrict your access token to. The date must be at least 1 day in the future. ![]() In the Expiration field, enter a token expiration period. (Optional) In the Description field, enter a description for your token. In the Token name field, enter a name for your token. This is recommended for interactive workflows such as a CLI.Ĭreating granular access tokens on the websiteĬlick Generate New Token, then click Granular Access Token. If you have two-factor authentication configured on your account, you will be required to enter a one-time passcode when using a publish token. Publish: A publish token can perform any action on your behalf, including downloading packages, publishing packages, and changing user settings or package settings. You can use an automation token in continuous integration workflows and other automation systems to publish a package even when you cannot enter a one-time passcode. This is recommended for automation and workflows where you are installing packages, but not publishing new ones.Īutomation: An automation token can download packages and publish new ones, but if you have two-factor authentication (2FA) configured on your account, it will not be enforced. It will have permission to read any private package that you have access to. Read-only: A read-only token can only be used to download packages from the registry. In the upper right corner of the page, click your profile picture, then click Access Tokens.Ĭlick Generate New Token, then select legacy token from the dropdown menu. Note: For greater security, we recommend using granular access tokens instead of legacy read-only tokens or legacy automation tokens.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |