TechPrufer
Get started
Cloudflare
Cloudflare logoCloudflare · Feature trail

Wrangler Authentication

2 posts · Sep 2019 – Feb 2023

What this trail covers

Cloudflare's Wrangler CLI has evolved its authentication process to improve the developer experience. Previously, users had to manually create API tokens through the Cloudflare dashboard. The new `wrangler login` command streamlines this by allowing users to authenticate directly with their Cloudflare credentials, similar to Argo Tunnel's login flow. This involves generating a public-private key pair, prompting the user to log in via the dashboard, automatically creating a Workers-scoped API token.

All Cloudflare trails
  1. So long, and thanks for all the deployments: deprecating Wrangler v1This post announces the deprecation of Wrangler v1 and strongly recommends upgrading to Wrangler v2. It explains the technical reasons for the rewrite (maintainability, complexity) and highlights key improvements in v2 such as offline development, zero-config startup, and developer tools support. It also details the migration process and encourages users to file issues for any blocking bugs.
  2. Bringing OAuth 2.0 to WranglerIntroduced OAuth 2.0 Authorization Code Flow with PKCE challenges for Wrangler CLI authentication, replacing cumbersome API token management with a more secure and user-friendly login process. This allows users to directly select required permissions (scopes) and revoke access via `wrangler logout`.
  3. Improving the Wrangler Startup ExperienceIntroduced `wrangler login` command for streamlined authentication, replacing manual API token creation. Implemented a flow where Wrangler generates an RSA key pair, prompts the user to open a dashboard page that creates a Workers-scoped API token, temporarily stores it in EdgeWorker Config Service (EWC), and then retrieves and uses it for authentication. This process uses asymmetric encryption to secure the token transfer.
  4. How We Design Features for Wrangler, the Cloudflare Workers CLIThis post details the iterative design process for adding Workers KV functionality to the Cloudflare Workers CLI (Wrangler). It outlines three attempts at designing the command-line interface, highlighting the challenges and lessons learned. The final design adopts a colon-delimited namespacing pattern (`kv:namespace`, `kv:key`, `kv:bulk`) for clarity and leverages the `wrangler.toml` file to map human-readable binding names to KV namespace IDs, improving user ergonomics.