0010611: merchant backend should support PATCHing the expiration time of token families

ID	Project	Category	View Status	Date Submitted	Last Update
0010611	Taler	merchant backend	public	2025-11-14 16:52	2026-02-04 19:00

Reporter	Florian Dold	Assigned To	Christian Grothoff	Resolution deadline
Implementer		Reviewer
Release signed by		Deployed by
Verifier		Communicator
Data protection authority notification required	No
CSIRT notification required	No
Estimated effort (hours)		Actual effort (hours)	0
Fast-track	No
Work package	none
Priority	normal	Severity	feature	Reproducibility	have not tried
Status	closed	Resolution	no change required
Product Version	1.0
Target Version	1.4	Fixed in Version	1.4

Summary	0010611: merchant backend should support PATCHing the expiration time of token families
Description	That way we can extend the validity of token families without having to configure a new token family, which would require coordination with the storefront configuration.
Tags	No tags attached.

Date Modified	Username	Field	Change
2025-11-14 16:52	Florian Dold	New Issue
2025-11-15 14:59	Christian Grothoff	Status	new => implementing
2025-11-15 14:59	Christian Grothoff	Product Version	=> 1.0
2025-11-15 14:59	Christian Grothoff	Target Version	=> 1.6
2025-12-19 19:13	Christian Grothoff	Relationship added	child of 0009057
2026-01-25 11:31	Christian Grothoff	Assigned To	=> Christian Grothoff
2026-01-25 11:31	Christian Grothoff	Status	implementing => assigned
2026-01-26 05:04	Christian Grothoff	Note Added: 0027358
2026-01-26 05:04	Christian Grothoff	Status	assigned => informing
2026-01-26 05:04	Christian Grothoff	Resolution	open => fixed
2026-01-26 05:04	Christian Grothoff	Fixed in Version	=> 1.4
2026-01-26 05:04	Christian Grothoff	Resolution	fixed => no change required
2026-01-26 05:04	Christian Grothoff	Target Version	1.6 => 1.4
2026-02-04 19:00	Christian Grothoff	Status	informing => closed

Christian Grothoff 2026-01-26 05:04 manager ~0027358	This is already in the spec (update valid_before) and also implemented in the backend (I checked the endpoint and DB logic). So there is nothing to do here. Alas, 0010549 and 0010612 are related bugs that must be fixed.