Today, Nx Cloud gets a huge upgrade to managing access to your cached artifacts using Nx Replay. Previously, workspaces were limited to defining access tokens with read or read/write permissions for an entire workspace. With the introduction of personal access tokens, you gain much more control over access. This is a feature request we've heard from many customers, especially our Enterprise customers, and we're happy to be able to deliver this enhancement.
Some link to: some link.
Access Tokens and the problem of revoking access
Our previous implementation of access tokens required you to commit the access token to your nx.json file. Typically, service providers don't recommend committing any kind of API token like this, and we've fielded a lot of questions about this practice in the past. It is safe to commit this token, as access to the cached artifacts of Nx Cloud rely on both the access token and the source code itself. Without access to both, you can't access the cache.
However, this did present the following problem: revoking someone's access to the cache became difficult as long as they had the source code. Imagine a scenario where someone has left an organization. As long as they have a clone of the repo, they have everything they need to access the cache, even if their credentials have been revoked. To fully revoke their access would require cycling the access token, which could interrupt the work of other developers and CI pipelines.
Access Tokens become CI Access Tokens
What we previously called "access tokens" will now be called "CI access tokens." They are still defined at the workspace level, but are designed for use in CI. These tokens should be set as environment variables or secrets on your CI platform so that they're no longer committed to your repo.
What are personal access tokens?
Personal access tokens are a new type of access token that is scoped to an individual user, rather than the workspace. This token authenticates the user with Nx Cloud when running tasks, so that we can validate their access to the distributed cache for a workspace. As soon as a user loses access to an Nx Cloud organization, they will no longer be able to access the cache for any of the organization's workspaces. The user's token belongs to them and will still allow access to their remaining organizations.
This gets even more powerful when combined with the GitHub VCS integration. When a user's GitHub access is removed from a GitHub-connected organization, their access to your Nx Cloud organization is removed, and their access to the cache for any of the organization's workspaces is removed. This means that Nx Cloud can fit into existing user de-provisioning processes you already have.
Open source teams also benefit from personal access tokens. You can configure your access to allow anonymous users to read from the cache, but limit read/write access to core contributors.
Controlling default access
By default, a workspace that opts in to personal access tokens will allow anonymous users (users without a personal access token defined) read-write access. This can be changed to disallow access to the cache for anonymous users in your workspace settings.
Users with personal access tokens will also have read-write access to the cache. This can be changed to enable read-only access in the workspace settings.
Converting existing workspaces to use personal access tokens
Personal access tokens can be enabled with Nx versions 13+. These steps will get you started, but you can find more details in our docs.
- Convert to using
nxCloudIdby runningnpx nx-cloud convert-to-nx-cloud-id- Previously, yournx.jsonhad a CI access token defined in thenxCloudAccessTokenproperty. This command will replace that withnxCloudId, a generic id that references your workspace but no longer provides access to the cache. - Generate a personal access token by running
npx nx login- Follow the directions in your terminal to log in to Nx Cloud. Each contributor with access to the workspace will need to complete this step. - Move CI access tokens to environment variables - Now that the access token is no longer committed to your
nx.json, you'll need to provide that CI access token via theNX_CLOUD_ACCESS_TOKENenvironment variable. - Recommended Disable anonymous access - By default, anyone without a personal access token will have read-write access to your cached artifacts. You can disable this anonymous access in your Nx Cloud workspace settings.
Learn more about using personal access tokens