Skip to main content
Paired approval apps authenticate with Ed25519 over a canonical string. This page is self-contained: you can implement a signer/verifier without access to any private repository. Scheme name: fau/1 device.

Algorithm

  1. Build the canonical string (UTF-8):
  1. Sign with Ed25519 (raw 32-byte secret).
  2. Send signature as base64url (no padding) in X-FAU-Signature.
Rules: Headers on the request:

Test keypair

For vectors only — never use in production. SHA-256 of empty string: e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855

Vectors

1. Bodyless GET (/papi/pending)

Why: commonest call — fetch pending approvals. Canonical:
Signature (base64url):

2. GET with query (/papi/activity?limit=50)

Why: query string must be inside the signed target. Canonical ends with the empty-body hash. Signature:

3. POST with JSON body

Why: body hash must match bytes exactly (no re-serialization after sign). Signature:
Note: the body string above is the vector’s literal bytes. Production decisions use values like deny / once / 30_days — the point of this vector is hashing, not the decision enum.

4. Lowercase method normalized

Input method post must sign as POST. Path /papi/pause, body {"paused":true}, timestamp 1760000003, nonce cGF1c2Utbm9uY2UtMDAxMg. Signature:

5. Non-ASCII JSON body

Body: {"note":"Café — naïve ☕ 東京"} (UTF-8). Path /papi/decide, timestamp 1760000004, nonce dW5pY29kZS1ub25jZS0wMQ. Signature:

How to use these vectors

  1. Implement canonicalization + sign + verify in your language.
  2. Assert your canonical string equals each vector’s canonical (byte-for-byte).
  3. Assert your signature verifies with the test public key (or matches exactly if your encoder is deterministic for the test secret).
  4. Only then wire production keys.
If vector 2 fails, you almost certainly signed /papi/activity without ?limit=50.