-
Notifications
You must be signed in to change notification settings - Fork 42
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 sign with estonian eID card #1281
Comments
This is fixed in the newest DigiDoc4 release. |
I am also having the same issue. @flokli, do you still have the same issue? |
@flokli actually, I just managed to do it following the information from : #1276
Set time-stamp service to "https://eid-dd.ria.ee/ts" in settings, and add the certificate above. |
Check NixOS/nixpkgs#334397. For some reason I don't have the issue (using NixOS unstable), but others seem to do. I recall once having added the SSL certificate to the qdigidoc config, but since then the config should have been removed again multiple times. |
Hey!
I've been getting reports by a user using the latest version of qdigidoc4 and libdigidocpp, and singing with their ID card to fail: NixOS/nixpkgs#334397. SmartID signing also seems to be broken, was some certificate error in April, now is stumbling over a TSL XML signature error.
The logs seem to suggest the default TSA URL configured in libdigidocpp to be unreachable:
There's also traces of this URL being changed in libdigidocpp, however, not in a release yet.
I switched out libdigidoc to this commit and restoring config defaults. It picks up another URL, but still complains about wrong SSL certificates there:
I also tried with
digidoc-tool
, it complaints about being unable to parse TSL XML files:I'm not quite sure if this is a bug in libdigidoc, it needing a new release, and/or a configuration failure at RIA's side. But it's currently preventing end users from makign signatures with their ID card.
Maybe there's a way to bring back the old
dd-at.ria.ee:80
endpoint until this all has been fixed and released.The text was updated successfully, but these errors were encountered: