In order to use API functions the license file and a certificate validation policy file are required along with the library files. Moreover ,certificates and private keys are used for signature creation.
The bundle you have downloaded includes a test license.You can specify the location of the license file by using License.setLicense(…) function. License files have become password protected since 1.4.0 version. Therefore the password of the license must also be provided by the user.
There is also a sample policy file in the package which can be usable without any change.
The API comes with the certificate store file used for certificate validation. In the policy file the location of the certificate store file can be configured. By default the API searches the certificate store file with the name “SertifikaDeposu.svt” in the folder “user_home/.sertifikadeposu”.
You need a certificate and the corresponding private key to create signature. PFX files are used store and transport certificates and private keys in password-protected form. You ca find a test pfx in the package. The numbers in the pfx file name denotes its password. You can either use the pfx file directly or store the certificates and private keys in it into a smartcard. PfxSigner class , included in the sample codes demonstrates how to get certificates from a pfx file and create signer using a pfx file.
Smartcard classes are not included in the Java SDK. Most IDEs have problem with building the code using the API. You have to disable prompting errors for restricted APIs in the configuration of the IDE.
