search

hyperledger-archives / fabric

THIS IS A READ-ONLY historic repository. Current development is at https://gerrit.hyperledger.org/r/#/admin/projects/fabric . pull requests not accepted
https://gerrit.hyperledger.org/
Apache License 2.0
1.17k stars 1.01k forks source link

Have a validity period in ECerts #474

Open elli-androulaki opened 8 years ago

elli-androulaki commented 8 years ago

This can be expressed in two ways (i) through the logical validity period we currently have in place and is used for TCerts, and (ii) through time, so that its human readible, but is not used for decisions being taken at the validator side. This issue should be worked out in collaboration with an issue updating the ECA such that it accepts ECerts renewal requests, and should not be addressed alone.

JonathanLevi commented 8 years ago

Interestingly enough, this came up over and over in some of our discussions. I am just going over some of the open issues (searched for E/TCerts) - so first of all, thanks for this. I agree, we need a form of validity period (in addition to the ability to retire/revoke too).

These days, we can/should probably also re-visit this by using a/the System Chaincode, which was not available/at our disposal when this issue was created.

christo4ferris commented 8 years ago

@elli-androulaki @JonathanLevi would one of you please move this to Jira and close this GH issue? Thanks

JonathanLevi commented 8 years ago

Yes, will do, thank you @christo4ferris.

@elli-androulaki: btw, I have allocated @dulcep to this item at her behest... but we can (and probably should!) collaborate on this... as the right way to do this IMO is to use the chaincode as noted above.

christo4ferris commented 8 years ago

can this be closed?

dulcep commented 8 years ago

Yes, please.

Tracked via FAB-142 , under the FAB-141 Epic and a few stories (e.g. supporting it on the Membership Services side, from the ClientSDK, specifying parameters statically and dynamically, etc.).