Privacy Pass Issuer (Draft 16) within Cloudflare Workers. Keys are stored in R2.

npm run deploy:production

Support:

• Public-Verifiable tokens (Blind-RSA)

All endpoints are public by default. Authentication should be a second layer. Internally, Cloudflare uses Access to protect /admin and /token-request endpoints.

One can test token issuance locally using npm run test:e2e -- <issuer-name> target. If the issuer uses mTLS (Mutual TLS), you can use npm run test:e2e -- --cert <path> --key <path> <issuer-name>.

Key rotation can be either manual, by calling POST /admin/rotate or automated by defining the ROTATION_CRON_STRING variable with a valid cron string and adding that same cron string value to the triggers.crons list.

Rotation of keys works by generating a new pair of private/public keys until it can find one whose token id doesn't conflict with a key pair already stored in the keys R2 Bucket. When it succeeds in generating that, it stores the new key pair in R2.

Keys become available as soon as they are stored in R2. The /.well-known/private-token-issuer-directory path directory immediately returns the new keys.

Note: Rotation does not delete any keys, and because the maximum amount of keys is 256 and the algorithm for generating them picks an id at random, if there are more than half of the maximum amount of keys, the time it takes to rotate increases. It's important that keys are cleared regularly, see Key Clearing.

Any cron string defined in triggers.crons that isn't equal to ROTATION_CRON_STRING or BACKUPS_CRON_STRING will trigger a key deletion. After these keys are deleted they can no longer be used by clients.

The project is licensed under the Apache-2.0 License.