@@ -70,6 +70,7 @@ <h3 id="features">Features</h3>
70
70
< li > < a href ="https://garantir.io/garasign/ "> GaraSign</ a > </ li >
71
71
< li > < a href ="https://cloud.google.com/security-key-management "> Google Cloud KMS</ a > </ li >
72
72
< li > < a href ="https://www.vaultproject.io "> HashiCorp Vault</ a > </ li >
73
+ < li > < a href ="https://www.signserver.org "> Keyfactor SignServer</ a > </ li >
73
74
< li > < a href ="https://www.oracle.com/security/cloud-security/key-management/ "> Oracle Cloud KMS</ a > </ li >
74
75
< li > < a href ="https://www.ssl.com/esigner/ "> SSL.com eSigner</ a > </ li >
75
76
</ ul >
@@ -228,6 +229,7 @@ <h4 id="attributes" class="mobile-only">Attributes</h4>
228
229
< li > < code > GOOGLECLOUD</ code > : Google Cloud KMS</ li >
229
230
< li > < code > HASHICORPVAULT</ code > : HashiCorp Vault</ li >
230
231
< li > < code > ORACLECLOUD</ code > : Oracle Cloud Key Management Service</ li >
232
+ < li > < code > SIGNSERVER</ code > : Keyfactor SignServer</ li >
231
233
< li > < code > TRUSTEDSIGNING</ code > : Azure Trusted Signing</ li >
232
234
</ ul >
233
235
</ td >
@@ -549,6 +551,7 @@ <h3 id="cli">Command Line Tool</h3>
549
551
- GOOGLECLOUD: Google Cloud KMS
550
552
- HASHICORPVAULT: HashiCorp Vault
551
553
- ORACLECLOUD: Oracle Cloud Key Management Service
554
+ - SIGNSERVER: Keyfactor SignServer
552
555
- TRUSTEDSIGNING: Azure Trusted Signing
553
556
-a,--alias <NAME> The alias of the certificate used for signing in the keystore
554
557
--keypass <PASSWORD> The password of the private key. When using a keystore,
@@ -880,6 +883,43 @@ <h4 id="example-hashicorpvault">Signing with HashiCorp Vault</h4>
880
883
--certfile full-chain.pem application.exe
881
884
</ pre >
882
885
886
+
887
+ < h4 id ="example-signserver "> Signing with Keyfactor SignServer</ h4 >
888
+
889
+ < p > < a href ="https://www.signserver.org "> SignServer</ a > is an on-premises open source signing service developed by Keyfactor.
890
+ SignServer supports various signing operations handled by signer workers. Jsign requires a
891
+ < a href ="https://doc.primekey.com/signserver/signserver-reference/signserver-workers/signserver-signers/plain-signer "> Plain Signer</ a >
892
+ worker configured with the < code > CLIENTSIDEHASHING</ code > or < code > ALLOW_CLIENTSIDEHASHING_OVERRIDE</ code > properties
893
+ set to < code > true</ code > , and the < code > SIGNATUREALGORITHM</ code > property set to < code > NONEwithRSA</ code > or
894
+ < code > NONEwithECDSA</ code > .</ p >
895
+
896
+ < p > The authentication is performed by specifying the username/password or the TLS client certificate in the
897
+ < code > storepass</ code > parameter. If the TLS client certificate is stored in a password protected keystore, the password
898
+ is specified in the < code > keypass</ code > parameter. The < code > keystore</ code > parameter references the URL of the
899
+ SignServer REST API. The < code > alias</ code > parameter specifies the id or the name of the worker. </ p >
900
+
901
+ < p > Authenticating with a username and a password:</ p >
902
+
903
+ < pre >
904
+ jsign --storetype SIGNSERVER \
905
+ --keystore https://example.com/signserver \
906
+ --storepass "<username>|<password>" \
907
+ --alias test \
908
+ application.exe
909
+ </ pre >
910
+
911
+ < p > Authenticating with a TLS client certificate:</ p >
912
+
913
+ < pre >
914
+ jsign --storetype SIGNSERVER \
915
+ --keystore https://example.com/signserver \
916
+ --storepass "/path/to/client-certificate.p12" \
917
+ --keypass <client-certificate-password> \
918
+ --alias test \
919
+ application.exe
920
+ </ pre >
921
+
922
+
883
923
< h4 id ="example-oraclecloud "> Signing with Oracle Cloud Key Management Service</ h4 >
884
924
885
925
< p > Signing with the Oracle Cloud Infrastructure Key Management Service requires the
0 commit comments