-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
Unable to run tests on some tokens with graphene-cli #85
Comments
A new mechanism was recently added in a PR, the test failure in CI has no relation to this issue here it seems. Hopefully, 51ff1b7 will fix it. |
There is a new change in the graphene-cli and it should make this work, see - PeculiarVentures/graphene-cli#5 We will need to update the capabilities documents for each document. |
@jspark311 can you see if this fixes your issue with the NitroKey? |
@nickrmc83 would you be able to re-run the Thales capabilities? |
I'll try and take a look tomorrow.
Nick
…On 26 Sep 2017 10:56 pm, "Ryan Hurst" ***@***.***> wrote:
@nickrmc83 <https://github.com/nickrmc83> would you be able to re-run the
Thales capabilities?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#85 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABhXUPh-5MqdL7Qoep9kP3tkHnZNEDgSks5smXL7gaJpZM4Pho-B>
.
|
I have a SafeNet 5100, I am able to enumerate the supported algorithms with grapgene-cli but I am not able to successfully execute the batch perf tests.
For example, here is a subset of capabilities:
If I run:
I think this is impacting our document signing cases with this token.
It also seems we are seeing something similar with a NitroKey #83
The text was updated successfully, but these errors were encountered: