The location and the password of the license file must be provided by using LicenseUtil.SetLicenseXml(…). By default the API searches for the license file in the 'license' folder in the working directory. LicenceUtil.setLicensePassword(…) is used in order to specify only the license password.The contents of the license file can be viewed via WordPad.

You can try ESYA API by using the test license included in the package. In the test license the value of the test field is set as “test”. You can only use the certificates with “test” valued subject field with the test license. Besides, a small delay happens on smartcard operations. There is a test pfx file including the certificates and private keys which can be used with the test license. The numbers in the name of the pfx file denotes its password. You can import the certificates and private keys into a smartcard with a pfx loader utility application. LoadPfx class included in the sample codes can also be used to do this.

It is absolutely required that the password of the license file is not shared with anyone in order to prevent unauthorized usage of the API. Since the license password is specified in the source code, we strongly recommend obfuscating your source code to avoid unwanted access to your license password by reverse engineering your packages. A seperate license password assigned for each customer which will not change upon renewal. Therefore you will not be required to update your code because of license renewal.

There is field named as maintenance agreement expiry date in the license file. You can use only the API versions which are created before this date. After the expiry date, you have to update the maintenance agreement in order to get new versions of the API.