Investigate JOSE library for Fastly Supported Crates and validate signing performance #70

Activity

1. jevansnyc

   assigned

   ChristianPavilonis

   on Oct 24, 2025
2. jevansnyc

   added the

   Task

   issue type on Oct 24, 2025
3. jevansnyc

   added a parent issue on Oct 24, 2025

   • Add request signing and key publishing for downstream verification #69
4. jevansnyc

   marked this as blocking 2 issues on Oct 24, 2025

   • As a publisher I want to introduce a simple method for downstream partners (particularly those buying impressions) to verify that I am the publisher that I say I am #71
   • As an SSP or DSP, I would like to cryptographically validate that an impression opportunity eminating from Trusted Server is authentic #72
5. ChristianPavilonis commented on Oct 24, 2025

   

   ChristianPavilonis

   on Oct 24, 2025

   Last edited by ChristianPavilonis

   Collaborator

   More actions

   I made a test service on fastly

   This creates a JWKS, and the /jws endpoint will generate some bytes as a payload, sign it (JWS) and add the signature to the header. It returns JSON with the payload and time measurement for the signing.

   Here's the repo

   What do you mean by "writing out to key store" are we saving signatures in fastly KV?
   Or do you want to just save the JWKS to fastly secrets? Which wouldn't be in the hot path.

   crates used:

   • jose-jws
   • jose-b64
   • jose-jwa
6. aram356

   closed this as completedon Oct 30, 2025
7. Tushar-kalsi commented on Nov 2, 2025

   

   Tushar-kalsi

   on Nov 2, 2025

   More actions

   @ChristianPavilonis please make this repo public which you created for test