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.

<h2>Mobil Signature Client</h2> <div class="level2"> <p> Mobile Signature Client API takes place in <code>infra</code> module of ESYA Signature API. The only difference from other signature types is the use of mobile device instead of smartcard for cryptographic signature creation operation. The sample code below, creates a mobile signature at client side. Only the lines with gray color are different from normal signature creation operation. </p> <p> <em><</em>sxh java;highlight:[8,9,10,11,12,13]> BaseSignedData bs = new BaseSignedData(); bs.addContent(new SignableByteArray("test".getBytes())); </p> <p> HashMap<em><</em>String, Object> params = new HashMap<em><</em>String, Object>(); ValidationPolicy policy= PolicyReader.readValidationPolicy(new FileInputStream(POLICY_FILE)); params.put(EParameters.P_CERT_VALIDATION_POLICY, policy); </p> <p> MSSPClientConnector connector = null; <em>Create a communication interface for your system. UserIdentifier user = new PhoneNumberAndOperator("05336564727", Operator.TURKCELL); ECertificate cert = connector.getCertificates(user)[0]; BaseSigner mobileSigner = new MobileSigner(connector, user, cert, "Doc1234 numaralı dökümanı imzayı onaylıyorum.", Algorithms.SIGNATURE_RSA_SHA1, null); bs.addSigner(ESignatureType.TYPE_BES, cert , mobileSigner, null, params); </em>write the contentinfo to file AsnIO.dosyayaz(bs.getEncoded(),SIGNATURE_FILE); <em><</em>/sxh> </p> <p> The communication between the client and the server is provided by the interface <code>MSSPClientConnector</code>. The information needed by the server API is sent via this interface. Since the communication technology may change from client to client, here , only an interface is defined. API users must implement this interface according to their own system and communication channels. </p> </div>