The UHPPOTE controller only accepts cards with a valid start and end date but there is a valid use case for uhppoted-httpd to allow a card to be created ahead-of-time without a start or end date. Assigning a default start/end date is not a solution because it potentially allows a temporary card to have unexpected access.
[x] Lowlight incomplete cards in the UI
[x] Only load valid'ish cards to the controller
[x] ACL
[x] Update simulator to reject cards without a valid start/end date
[x] Add simulator REST API to create cards without valid start/end dates for testing
Ref.:
The UHPPOTE controller only accepts cards with a valid start and end date but there is a valid use case for uhppoted-httpd to allow a card to be created ahead-of-time without a start or end date. Assigning a default start/end date is not a solution because it potentially allows a temporary card to have unexpected access.
incomplete
cards in the UI