Skip to content

Commit

Permalink
Conditionalise use of --pkcs11Config option to XmlSecTool.
Browse files Browse the repository at this point in the history
Only supply the option if there is a PKCS11 configuration file
specified, so that we can also sign using non-PKCS11 methods if
required.
  • Loading branch information
iay committed Aug 1, 2016
1 parent 65c2123 commit c6b87d9
Showing 1 changed file with 5 additions and 7 deletions.
12 changes: 5 additions & 7 deletions build.xml
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@
* "ant push" sends all files to the remote site, and requires
the remote site password.
-->
<project default="echoproperties">
<project default="echoproperties" xmlns:if="ant:if" xmlns:unless="ant:unless">

<!--
*******************************************
Expand Down Expand Up @@ -654,13 +654,11 @@
<arg value="@{digest}"/>

<!--
Sign using pkcs11Config with keystoreProvider
This only works with XmlSecTool 1.2.0 and later.
It requires the java.security file to be unmodified.
If we have a PKCS11 configuration specified, include it.
-->
<arg value="--pkcs11Config"/>
<arg value="${keystore.pkcs11.config}"/>
<arg if:set="keystore.pkcs11.config" value="--pkcs11Config"/>
<arg if:set="keystore.pkcs11.config" value="${keystore.pkcs11.config}"/>

<arg value="--keystoreProvider"/>
<arg value="sun.security.pkcs11.SunPKCS11"/>

Expand Down

0 comments on commit c6b87d9

Please sign in to comment.