Project

Profile

Help

Story #7701

Make SigningService in the DB immutable

Added by bmbouter 8 months ago. Updated 7 months ago.

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

100%

Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
No
Tags:
Sprint:
Sprint 85
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.

Associated revisions

Revision 5fff2a9d View on GitHub
Added by Lubos Mjachky 8 months ago

Raise an error when a user tries to update a signing service

closes #7701

History

#1 Updated by mdellweg 8 months ago

  • Groomed changed from No to Yes

#2 Updated by mdellweg 8 months ago

  • Sprint set to Sprint 84

#3 Updated by lmjachky 8 months ago

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

#4 Updated by pulpbot 8 months ago

  • Status changed from ASSIGNED to POST

#5 Updated by rchan 8 months ago

  • Sprint changed from Sprint 84 to Sprint 85

#6 Updated by Anonymous 8 months ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#7 Updated by daviddavis 7 months ago

  • Sprint/Milestone set to 3.9.0

#8 Updated by pulpbot 7 months ago

  • Status changed from MODIFIED to CLOSED - CURRENTRELEASE

Please register to edit this issue

Also available in: Atom PDF