-
Notifications
You must be signed in to change notification settings - Fork 516
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Revocation API using anoncreds-rs #2458
Revocation API using anoncreds-rs #2458
Conversation
Signed-off-by: Jason Sherman <[email protected]>
Signed-off-by: Jason Sherman <[email protected]>
…remove extraneous methods Signed-off-by: Jason Sherman <[email protected]>
add a revocation api to test endpoints without endorser (not yet added to anoncreds) Signed-off-by: Jason Sherman <[email protected]>
implement endpoints used for TAA BDD tests Signed-off-by: Jason Sherman <[email protected]>
@dbluhm - bumping this if you have time to look over the updates since your last review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Couple of corrections
…ions Signed-off-by: Jason Sherman <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
thanks for the extra pair of eyes @dbluhm. tests and everything work but having the wrong methods in the base class sure would have been confusing for other implementations. |
See issue #2432.
Trim down
/revocation
API to match up with/anoncreds/revocation
API.Removed APIs related to
Manually Creating Revocation Entries
.Updated the pytests to use
@pytest.mark.skip(reason="anoncreds-rs breaking change")
instead of renaming the tests. Still need to come back to these and fix them (see issue #2433).There are remaining related issues - need to update TAA related APIs - see #2493 - but want to close this out and tackle that separately. (Update, these endpoints are now implemented/updated). Closes #2493
We will also have to discuss if we need to add back the
Manually Creating Revocation Entries
API as they were very handy during the IDIM reset/issues.Since we do not have endorser enabled, I simply couldn't update/use the BDD tests in
0586-sign-transaction.feature
so I did hack together something similar that did not require an endorser. I ran againstmain
and all the scenarios passed, but the included file has 1 scenario skipped because the Manual steps/API do not exist here.