Activity for SignServer
-
Markus Kilås created a blog post
SignServer Community 7.3.2
-
SignServer released /signserver/7.3/README.md
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Marcus Lundblad created a blog post
SignServer Community 7.1.1
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
SignServer Community 7.0
-
SignServer Community 7.0
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
martin Edward corr posted a comment on discussion Help
An old thread but I had the same issue and resolved it as follows. The problem was that I had installed ejbca several times and got the ManagementCA root certificates mixed up. I discovered the issue by comparing the root ca serial number to the one encoded in the p12 chain and could see they were different. I cleared all installs out, cleared all certs keys pem p12 crt files then did a fresh install of ejbca then signserver, followed the guides and that sorted it. hope this helps.
-
iniesta mbaye posted a comment on discussion Open Discussion
Hello Adrian Rose Jayanto, how were you able to resolve your error? I am currently facing the same issue.
-
Hi Jonathan, SignServer discussions moved to https://github.com/Keyfactor/signserver-ce/discussions. Cheers, Markus
-
Hi Nicolas, SignServer discussions moved to https://github.com/Keyfactor/signserver-ce/discussions. Cheers, Markus
-
Jonathan KALFA posted a comment on discussion Help
Hi, In the documentation I read they can send for one call : REQUEST_METADATA.VISIBLE_SIGNATURE_RECTANGLE REQUEST_METADATA.VISIBLE_SIGNATURE_PAGE For a call of type : MultipartBody prepareRequest = Unirest.post(URL_API_PRODUCTION + "/process") .field("workerName", "PDFSigner") .field("processType", "signDocument") .field("filereceivefile", file); But in some case, we have two or more signature one the same document. Should we send an API call "for each signature"? or is there a way to send a document...
-
Nicolas Veiguela posted a comment on discussion Help
Hello everyone, I'm working with SignServer and need to set up a Certificate Authority (CA) that can issue certificates for each signing worker without requiring a physical USB token. The certificates need to be recognized by Adobe, showing the signer's name but indicating that the approval comes from our organization via the SignServer CA. For testing or if we don't have a CA in our organization, we can set up our own PKI using software like EJBCA or OpenSSL. Could someone guide me on: How to install...
-
SignServer CE 6.3.0.Final
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Tomas Gustavsson posted a comment on discussion Help
Hi Pham, SignServer discussions moved to https://github.com/Keyfactor/signserver-ce/discussions. My guess is that you have not added your wildfly user to the "hsmusers" group. This is needed.
-
Pham Hieu posted a comment on discussion Help
I have same issue, I only have user root to login server and run vtl verify. But I start wildfly with an user like 'wildfly', is this the problem.
-
Thu Huong posted a comment on discussion Help
Hi Archil, I encountered the same problem with you, I got ManagementCA.pem and p12 file from EJBCA and when start signserver I using ManagemetCA.pem then import p12 file in my browser to tell the browser that I have cert here. But I got error "Connection is not secure, your certificate is invalid". I dont know where it go wrong. Can you solve this problem successfully?
-
SignServer CE 6.2 is released
-
SignServer CE 6.2 is released
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1 >
