Pulp

Background¶

A public discussion was had on June 10th https://youtu.be/uecwUFJTWno and minutes taken here: https://hackmd.io/k5xm4WZ7QpeX0HF80XS9OQ

It was determined there that having the public key on the SigningService model itself (saved in the db) is a good thing because right now flowing the public key over and over again over the call interface takes more work and is not helpful to the design. In all SigningServices there will be exactly one public key. Keeping this well-known makes everything easier including validating signed data returned from the signing service.

Todo¶

Add a TextField named public_key to the SigningService model.