You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently we compute revoked based on valid_until date. We would like to be able to "force" revoke an indicator with revoked input parameter, which already exists.
One use case is we receive data of an indicator with a valid_from date and revoked: true, but no valid_until date. Currently we ignore the revoked parameter and set it according to a valid_until date that we compute (based on indicator lifetime).
Proposed Solution
We should save the revoked input when we don't have a valid_until date.
SouadHadjiat
changed the title
Handle revoke input for Indicators without valid_until date
Handle revoked input for Indicators without valid_until date
Feb 23, 2024
Use case
Currently we compute
revoked
based onvalid_until
date. We would like to be able to "force" revoke an indicator withrevoked
input parameter, which already exists.One use case is we receive data of an indicator with a valid_from date and
revoked: true
, but no valid_until date. Currently we ignore the revoked parameter and set it according to a valid_until date that we compute (based on indicator lifetime).Proposed Solution
We should save the
revoked
input when we don't have a valid_until date.Additional Information
From this community slack conversation : https://filigran-community.slack.com/archives/C06CF1N302W/p1708686009120799
The text was updated successfully, but these errors were encountered: