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
Since this section is talking about registration, why is refresh paradigm left dangling at the end. Is it thought to use this same method to ask for a refresh? I can see getting a new receipt, but that may fail due to the time validity of the signed statement. If you expect it to be based on previous data on the log, then it needs to be indexed based on the previous receipt.
The text was updated successfully, but these errors were encountered:
Sounds sensible. Something like '/reissue?receiptid=xyzy
Where 'xyzy' is the durable ID of a receipts that is already included in the log (I'm being deliberately obtuse with the ID format since that's under question in a separate Issue).
Please submit a PR that matches your use case needs.
Since this section is talking about registration, why is refresh paradigm left dangling at the end. Is it thought to use this same method to ask for a refresh? I can see getting a new receipt, but that may fail due to the time validity of the signed statement. If you expect it to be based on previous data on the log, then it needs to be indexed based on the previous receipt.
The text was updated successfully, but these errors were encountered: