Project

Profile

Help

Story #7700

Add public_key to the SigningService model itself

Added by bmbouter 3 months ago. Updated about 15 hours ago.

Status:
POST
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
% Done:

0%

Estimated time:
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.

History

#1 Updated by mdellweg 3 months ago

  • Groomed changed from No to Yes

#2 Updated by mdellweg 3 months ago

  • Sprint set to Sprint 84

#3 Updated by lmjachky 3 months ago

  • Status changed from NEW to ASSIGNED
  • Assignee set to lmjachky

#4 Updated by rchan 3 months ago

  • Sprint changed from Sprint 84 to Sprint 85

#5 Updated by pulpbot 3 months ago

  • Status changed from ASSIGNED to POST

#6 Updated by rchan 2 months ago

  • Sprint changed from Sprint 85 to Sprint 86

#7 Updated by rchan about 2 months ago

  • Sprint changed from Sprint 86 to Sprint 87

#8 Updated by rchan about 1 month ago

  • Sprint changed from Sprint 87 to Sprint 88

#9 Updated by rchan about 15 hours ago

  • Sprint changed from Sprint 88 to Sprint 89

Please register to edit this issue

Also available in: Atom PDF