ESYAE-imza Kütüphaneleri

Bu sayfa salt okunur. Kaynağı görebilirsiniz ama değiştiremezsiniz. Bunun yanlış olduğunu düşünüyorsanız yöneticiye danışın.

<h1>License Settings</h1> <div class="level1"> <p> The location and the password of the license file must be provided by using <code>LicenseUtil.SetLicenseXml(…)</code>. By default the API searches for the license file in the 'license' folder in the working directory. <code>LicenceUtil.setLicensePassword(…)</code> is used in order to specify only the license password.The contents of the license file can be viewed via WordPad. </p> </div> <h2>1. Working with the Test License</h2> <div class="level2"> <p> 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. </p> </div> <h2>2. The Security of the License File</h2> <div class="level2"> <p> 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. </p> </div> <h2>3. Bakım Sözleşme Bitiş Tarihi</h2> <div class="level2"> <p> Lisans dosyanızda bakım sözleĢme bitiş tarihi ile belirtilen bir alan bulunmaktadır. Bu tarihten daha önce yayınlanan kütüphane sürümlerini kullanmaya devam edebilirsiniz. Bu tarihten sonra yayınlanan kütüphane sürümlerini kullanabilmeniz için bakım sözleşmesi yapmanız gerekecektir. </p> </div>