Project

Profile

Help

Story #7701

Make SigningService in the DB immutable

Added by bmbouter 7 days ago. Updated about 2 hours ago.

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

0%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 84
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 making the SigningService model itself immutable is a good thing for these reason:

  • Content signers should be able to leave their existing publications pointing to the old SigningService, otherwise their data will become invalidated.
  • Content signers should have to take explicit action when a public key is rotated, especially so they can know to also update clients.

Todo

Make it immutable, the data contained in a SigningService, or its subclass should not be modified once saved.

History

#1 Updated by mdellweg 7 days ago

  • Groomed changed from No to Yes

#2 Updated by mdellweg about 2 hours ago

  • Sprint set to Sprint 84

Please register to edit this issue

Also available in: Atom PDF