Installation of jPOS

this section describes how to install and configure jpos template to work with the {{vectera}} before starting this section, download jpos template from the github repository within a jpos project, add a reference to the excrypt jar dependencies { compile files('your/path/to/jpos excrypt 1 0 5 snapshot jar') } run gradle installresources to add the following qbean configuration samples to the project dist \| deploy \| | 20 excrypt xml \| ` 90 excrypt ping xml ` deploy cli ` 20 excrypt xml change the configuration values in 20 excrypt xml as needed excrypt adapter the excryptadapter class encapsulates all the excrypt command set implementation it implements the smadapter interface so it can be configured and deployed as any other jpos smadapter implementation example ( 20 excrypt xml ) \<ssm name="excrypt" class="org jpos q2 security smadaptor" logger="q2"> \<attr name="impl">org jpos security excrypt excryptadapter\</attr> \<property name="host" value="us01hsm01test virtucrypt com" /> \<property name="port" value="6000" /> \<property name="pkcs12" value="cfg/certificate p12" /> \<property name="passphrase" value="your passphrase" /> \</ssm> configuration property description host excrypt host (i e us01hsm01test virtucrypt com) port excrypt port (i e 6000) pkcs12 path to the pkcs #12 file (i e cfg/certificate p12) passphrase passphrase for the pkcs #12 file accessing the adapter the excrypt adapter instance can be pulled off the name registrar by doing the following excryptadapter excrypt = nameregistrar get("excrypt"); // or smadapter adapter = nameregistrar get("excrypt"); // recommended by doing the latter, the code produced will not have a direct dependency to the excrypt implementation and will, potentially, work with any other underlying smadapter implementation (i e jcesecuritymodule ) environment provider the excrypt library provides a custom environment provider that helps secure configuration values example in cfg/default yml example config hsm ujnsgpw1x8edx2yuqp5koolxtmzjxgqyto9frsljwss0hqtlpivrf1dnpxf9hpd when loading up the example config value, the system will decrypt value on the fly using the hsm the encrypted value is calculated using the encrypt cli command (see validate and test docid\ iagyt5mv48cf6wfj9ftek ) if you would like to make the configuration values more secure, you can store the values in cfg/default yml excrypt host us01hsm01test virtucrypt com excrypt port 3070 excrypt pkcs12 / / /application certificate p12 excrypt passphrase obf jh8jyaaaaali8hdvspkjqass4iullxu= hsm service excrypt key obf es3vegaaacd3ueb2ujnsgpw1x8edx2yuqp5koolxtmzjxgqyto9frsljwss0hqtlpi note that sensitive configuration values have been obfuscated using jpos' obf cli command this practice is recommended and will help avoid leaking configuration values to occasional viewers for more information on the configuration sub system and the obf environment provider, see the jpos programmer's guide , section 3 3 then you can modify the values in 20 excrypt yml \<ssm name="excrypt" class="org jpos q2 security smadaptor" logger="q2"> \<attr name="impl">org jpos security excrypt excryptadapter\</attr> \<property name="host" value="${excrypt host}" /> \<property name="port" value="${excrypt port}" /> \<property name="pkcs12" value="${excrypt pkcs12}" /> \<property name="passphrase" value="${excrypt passphrase}" /> \</ssm>