Actions
Story #7700
closed
Add public_key to the SigningService model itself
Start date:
Due date:
% Done:
100%
Estimated time:
(Total: 0:00 h)
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 89
Quarter:
Description
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.
Related issues
Updated by lmjachky almost 2 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to lmjachky
Updated by pulpbot almost 2 years ago
- Status changed from ASSIGNED to POST
Added by Lubos Mjachky over 1 year ago
Updated by Anonymous over 1 year ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulpcore|2e0366013d2035c96156bf83debdfc7c03f647a0.
Updated by pulpbot over 1 year ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Updated by quba42 over 1 year ago
- Related to Issue #8307: Signing Service is broken by pulpcore change added
Actions
.
Add a new field that holds the value of the public key to SigningService
closes #7700