<?xml version="1.0" encoding="utf-8"?>
<!-- generator="FeedCreator 1.7.2-ppt DokuWiki" -->
<?xml-stylesheet href="https://yazilim.kamusm.gov.tr/esya-api/lib/exe/css.php?s=feed" type="text/css"?>
<rss version="2.0">
    <channel>
        <title>ESYA en:esya:cades</title>
        <description></description>
        <link>https://yazilim.kamusm.gov.tr/esya-api/</link>
        <lastBuildDate>Wed, 29 Apr 2026 19:07:07 +0000</lastBuildDate>
        <generator>FeedCreator 1.7.2-ppt DokuWiki</generator>
        <image>
            <url>https://yazilim.kamusm.gov.tr/esya-api/lib/tpl/dokuwiki/images/favicon.ico</url>
            <title>ESYA</title>
            <link>https://yazilim.kamusm.gov.tr/esya-api/</link>
        </image>
        <item>
            <title>en:esya:cades:eimza-cades-kutuphanesi</title>
            <link>https://yazilim.kamusm.gov.tr/esya-api/doku.php?id=en:esya:cades:eimza-cades-kutuphanesi&amp;rev=1378119274&amp;do=diff</link>
            <description>This document ESYA provides an introductory summary on how to use ESYA CMS Signature API. With CMS Signature API you can manage your keys with smartcards, validate certificates, create and verify electronic signatures. 
API requires a valid license.

You need a digital certificate and a secure container for the private key in order to create signature. Usually  smartcards are used as the secure container for the private keys. For detailed information about signature creation please refer to the …</description>
        <category>en:esya:cades</category>
            <pubDate>Mon, 02 Sep 2013 10:54:34 +0000</pubDate>
        </item>
        <item>
            <title>en:esya:cades:imza-atma</title>
            <link>https://yazilim.kamusm.gov.tr/esya-api/doku.php?id=en:esya:cades:imza-atma&amp;rev=1377763486&amp;do=diff</link>
            <description>Signature Creation

Signature creation consists of two steps which are the validation of the signing certificate and creation of the signature.

Signing an Unsigned Document

BaseSignedData is responsible for data signing. Firstly, by using the method addContent(...) the data to be signed must be defined. This method must be called only once. The data to be signed can not be modified once it is assigned by addContent(...). The signer information is defined by using addSigner(...). This function …</description>
        <category>en:esya:cades</category>
            <pubDate>Thu, 29 Aug 2013 08:04:46 +0000</pubDate>
        </item>
        <item>
            <title>en:esya:cades:imza-dogrulama</title>
            <link>https://yazilim.kamusm.gov.tr/esya-api/doku.php?id=en:esya:cades:imza-dogrulama&amp;rev=1378127809&amp;do=diff</link>
            <description>Signature Verification

Signature verification is a series of operations performed by the signature checkers. These checkers consist of structural checkers and signing certificate checker. The certificate checker performs the structural validation  chain validation and revocation status control for a signing certificate. Certificate revocation status control needs CRL or OCSP Response valid in signing time. Certificate validation requires validation policy file. This XML file can be configured b…</description>
        <category>en:esya:cades</category>
            <pubDate>Mon, 02 Sep 2013 13:16:49 +0000</pubDate>
        </item>
        <item>
            <title>en:esya:cades:imza-donusum</title>
            <link>https://yazilim.kamusm.gov.tr/esya-api/doku.php?id=en:esya:cades:imza-donusum&amp;rev=1378128086&amp;do=diff</link>
            <description>Conversion Between Signature Types

The conversion between signature types can be performed by using the class BaseSignedData. Firstly, the list of the signers are accessed by the method BaseSignedData.getSignerList() from the signed document. Then the signer to be converted is found in the list and the method convert() of the signer is called.
The sample code below converts a BES signature to EST:</description>
        <category>en:esya:cades</category>
            <pubDate>Mon, 02 Sep 2013 13:21:26 +0000</pubDate>
        </item>
        <item>
            <title>en:esya:cades:imza-ozellikleri</title>
            <link>https://yazilim.kamusm.gov.tr/esya-api/doku.php?id=en:esya:cades:imza-ozellikleri&amp;rev=1378117451&amp;do=diff</link>
            <description>Optional Attributes

You can add  optional information such as signing time, adress as attributes into the signature. The list of attributes deifned in the API is as follows;
 SigningTimeAttr  Contains stated signing time. It does not guarantee the exact signing time and is only used for informational purposes.   SignerLocationAttr  Includes information about signer's address. Country, city and postal code might be included. Since it is only for informational purposes, some of its fields can be …</description>
        <category>en:esya:cades</category>
            <pubDate>Mon, 02 Sep 2013 10:24:11 +0000</pubDate>
        </item>
        <item>
            <title>en:esya:cades:imza-parametreler</title>
            <link>https://yazilim.kamusm.gov.tr/esya-api/doku.php?id=en:esya:cades:imza-parametreler&amp;rev=1378293425&amp;do=diff</link>
            <description>Parameters

API needs some parameters for signature creation and verification operations which differ according to the signature type. The following table lists basic parameters and their usage. For the complete list, see EParameters.
 P_EXTERNAL_CONTENT  The content that is signed. It must be an object of ISignable   P_CONTENT_TYPE  The content type. By default, it is “1, 2, 840, 113549, 1, 7, 1” which means “data”. P_CERT_VALIDATION_POLICY  Certificate Validation Policy to be used in validatio…</description>
        <category>en:esya:cades</category>
            <pubDate>Wed, 04 Sep 2013 11:17:05 +0000</pubDate>
        </item>
        <item>
            <title>en:esya:cades:imza-tipleri</title>
            <link>https://yazilim.kamusm.gov.tr/esya-api/doku.php?id=en:esya:cades:imza-tipleri&amp;rev=1390297269&amp;do=diff</link>
            <description>Creating Different Signature Types

This section provides brief explanations for the signature types that are frequently used. 
You should read the document “E-Signature  Profiles” before deciding on which signature type is proper for you. 
See the document TS ETSI 101 733 for detailed information about signature types.</description>
        <category>en:esya:cades</category>
            <pubDate>Tue, 21 Jan 2014 09:41:09 +0000</pubDate>
        </item>
        <item>
            <title>en:esya:cades:imza-zamani</title>
            <link>https://yazilim.kamusm.gov.tr/esya-api/doku.php?id=en:esya:cades:imza-zamani&amp;rev=1378212371&amp;do=diff</link>
            <description>Signing Time

Signing time can be determined in several ways;

	*  	Timestamp
	*  	Signing Time Signed Attribute
	*  	External Time Parameter

Timestamps are the most secure source of time.

Timestamp

Timestamp guarantees the existence of a certain data at some specified time.Since ,in our context, the timestamp is taken over the signature, it proves the existence of the signature at the specified time. Timestamps are generated by trusted authorities. All Electronic Certificate Service Provider…</description>
        <category>en:esya:cades</category>
            <pubDate>Tue, 03 Sep 2013 12:46:11 +0000</pubDate>
        </item>
        <item>
            <title>en:esya:cades:sertifika-dogrulama</title>
            <link>https://yazilim.kamusm.gov.tr/esya-api/doku.php?id=en:esya:cades:sertifika-dogrulama&amp;rev=1378119215&amp;do=diff</link>
            <description>Certificate Validation

Before signature creation, the certificate must be validated. Thus, creation of invalid signatures due to invalid signing certificates is avoided. The certificate validation can be disabled by using parameters. You can see the parameter P_VALIDATE_CERTIFICATE_BEFORE_SIGNING in section Parameters.</description>
        <category>en:esya:cades</category>
            <pubDate>Mon, 02 Sep 2013 10:53:35 +0000</pubDate>
        </item>
    </channel>
</rss>
