# PDFSign Component

The PDFSign component signs PDF documents.

## Syntax

```text
nsoftware.SecurePDF.PDFSign
```

## Remarks

The PDFSign component can sign PDF documents in accordance with a selection of PDF and PAdES signature standards, including basic Adobe signatures (ISO 32000) and PAdES signatures (ETSI EN 319 142-1).

### Preparing the Signature

 To configure PDFSign to produce the desired signature, first provide the input document as a file ([InputFile](#inputfile-property-pdfsign-component)), byte array ([InputData](#inputdata-property-pdfsign-component)), or stream ([SetInputStream](#setinputstream-method-pdfsign-component)) and assign your signing certificate to the [SigningCert](#signingcert-property-pdfsign-component) property. Then indicate where to save the output document by setting [OutputFile](#outputfile-property-pdfsign-component) or calling [SetOutputStream](#setoutputstream-method-pdfsign-component).

Optionally, specify the *Signature** properties and the [TimestampServer](#timestampserver-property-pdfsign-component) property, and adjust any chain validation parameters as necessary (please see the [Chain Validation Setup](#chain-validation-setup) section for more details). Finally, call [Sign](#sign-method-pdfsign-component).

PDFSign also provides means to customize the appearance of the signature widget to be shown on the document page. You can create your own signatures (e.g., in the form of your company's logo) by adjusting the widget properties available in the [SetWidgetProperty](#setwidgetproperty-method-pdfsign-component) method. Alternatively, you can choose not to associate any widget with your signature by setting the *Invisible* widget property to *true*. Please see [this article](https://www.nsoftware.com/kb/articles/securepdf-widgets) for more details about customizing the signature widget.

### The Signing Process

 Depending on the configuration, the signing process may be as straightforward as calculating the document hash and signing it with the private key, or it may involve the advanced chain validation routine. During the latter process, the component may contact external revocation (i.e., CRL and OCSP endpoints) and trust sources to establish the validity of the signing certificate.

If an external TSA server was provided by the [TimestampServer](#timestampserver-property-pdfsign-component) property, the component also contacts it to timestamp the new signature.

During signing, PDFSign may fire events to notify your code about certain conditions. For example, if the input document is encrypted but no decryption parameters were found in the [Password](#password-property-pdfsign-component) or [DecryptionCert](#decryptioncert-property-pdfsign-component) properties, the component fires either the [Password](#password-event-pdfsign-component) or [RecipientInfo](#recipientinfo-event-pdfsign-component) event to tell your code that it needs decryption information to be able to continue with the signing. Additionally, the [SSLServerAuthentication](#sslserverauthentication-event-pdfsign-component) event fires if one of the HTTP endpoints involved during the operation (which may be a TSA, CRL, OCSP, or Trusted List service) operates over TLS and needs its certificate to be validated.

**Remote Signing**

PDFSign can also be configured to sign with external keys. In such scenarios, the component handles every aspect of the signing routine except the actual signing operation - including the document hash calculation, preparation of signature objects, and CRL/OCSP retrieval. Instead of calculating the signature by itself, the component requests it from your code and later incorporates it into the document.

To enable this mode, set the [RemoteSignatureMethod](#remotesignaturemethod-property-pdfsign-component) property to either *rsmPKCS1* or *rsmPKCS7* and call [Sign](#sign-method-pdfsign-component). The component outputs a "pre-signed" document, which encapsulates any signature and widget settings, and populates the [RemoteSignatureDigest](#remotesignaturedigest-property-pdfsign-component) property with the raw data to be signed.

Which remote signing method to use depends on the specifics of your remote signing engine. With PKCS#1, the public copy of the signing certificate is needed on the first step because it is included in the PKCS#7 structure prepared by the component. With PKCS#7 on the other hand, only the document hash is calculated, which does not require the certificate.

Once your remote signing engine signs the hashed data with the private key, pass the resulting signed data back to the component via the [RemoteSignatureData](#remotesignaturedata-property-pdfsign-component) property to embed it into the document.

The following code shows the full PKCS#1 remote signing process:

```csharp
// Step 1: Pre-sign
pdfsign.InputFile = "input.pdf";
pdfsign.OutputFile = "presigned.pdf";
pdfsign.SigningCert = new Certificate(CertStoreTypes.cstPublicKeyFile, "cert.cer", "", "*");
// Configure signature and/or widget properties as desired
pdfsign.RemoteSignatureMethod = PDFSignRemoteSignatureMethods.rsmPKCS1;
pdfsign.Sign();
string toBeSigned = pdfsign.RemoteSignatureDigest;

// Step 2: Pass to remote signing engine
byte[] signedData = SignData(toBeSigned);

// Step 3: Finalize
pdfsign.Reset();
pdfsign.InputFile = "presigned.pdf";
pdfsign.OutputFile = "signed.pdf";
pdfsign.RemoteSignatureData = HexEncode(signedData);
pdfsign.Sign();
```

 In the PKCS#7 method, the component can additionally act as the remote signer. To implement this side of the scheme, provide a binary hash of the PDF as input and set [RemoteSignatureMethod](#remotesignaturemethod-property-pdfsign-component) to *rsmDigest*. After [Sign](#sign-method-pdfsign-component) completes, the output will contain a signed binary PKCS#7 structure over the hash that can then be embedded into the pre-signed document.

The following code shows the full PKCS#7 remote signing process using PDFSign on both sides:

```csharp
// Step 1: Pre-sign
pdfsign.InputFile = "input.pdf";
pdfsign.OutputFile = "presigned.pdf";
// Configure signature and/or widget properties as desired
pdfsign.RemoteSignatureMethod = PDFSignRemoteSignatureMethods.rsmPKCS7;
pdfsign.Sign();
string toBeSigned = pdfsign.RemoteSignatureDigest;

// Step 2: Sign the hash
pdfsign.Reset();
pdfsign.InputData = HexDecode(toBeSigned);
pdfsign.SigningCert = new Certificate(CertStoreTypes.cstPFXFile, "cert.pfx", "password", "*");
pdfsign.ValidationPolicy = PDFSignValidationPolicies.vpNone;
pdfsign.RemoteSignatureMethod = PDFSignRemoteSignatureMethods.rsmDigest;
pdfsign.Sign();
byte[] signedData = pdfsign.OutputData;

// Step 3: Finalize
pdfsign.Reset();
pdfsign.InputFile = "presigned.pdf";
pdfsign.OutputFile = "signed.pdf";
pdfsign.RemoteSignatureData = HexEncode(signedData);
pdfsign.Sign();
```

### Basic Adobe Signatures

 A basic (also known as legacy) Adobe signature is an original Adobe Acrobat document signature. This is an outdated form of PDF signature; although PAdES is loosely built on it, this signature type does not support extended features and is not compliant with PAdES. Unless the recipient of your signed documents expects you to specifically use this kind of signature, it is unlikely that you will ever need it.

### PAdES Signatures and Profiles

 In PAdES, a given signature's profile describes the level of "completeness" of the validation material (i.e., certificates, CRLs, and OCSP responses) included in the signature. For example, signatures compliant with the PAdES B-B or PAdES B-T profiles do not require any validation material at all, whereas signatures compliant with the PAdES B-LTA profile must contain complete validation material.

**PAdES B-B**

The PAdES B-B profile is the baseline profile that uses the PAdES-BES signature level by default, meaning the signature contains only the signing time and signer information.

Use the following code to create a B-B signature:

```csharp
pdfsign.InputFile = "input.pdf";
pdfsign.OutputFile = "signed.pdf";
pdfsign.SigningCert = new Certificate(CertStoreTypes.cstPFXFile, "cert.pfx", "password", "*");
pdfsign.SignatureProfile = PDFSignSignatureProfiles.pfBaselineB;
pdfsign.ValidationPolicy = PDFSignValidationPolicies.vpNone;
pdfsign.Sign();
```

 **PAdES-EPES**

To instead create a PAdES-EPES signature that includes the signature-policy-identifier attribute, set the [PolicyHash](#PolicyHash), [PolicyHashAlgorithm](#PolicyHashAlgorithm), and [PolicyId](#PolicyId) configuration settings before calling [Sign](#sign-method-pdfsign-component).

This profile, in both the BES and EPES settings, creates a basic signature that remains valid as long as the signing certificate has not expired or been revoked. Signatures at this level need not contain any validation material.

**PAdES B-T**

The PAdES B-T profile extends the basic BES or EPES signature by adding a signature timestamp. This timestamp certifies that the signature was created at a specific moment in time. Similar to the B-B profile, signatures at this level need not contain any validation material.

Use the following code to create a B-T signature:

```csharp
pdfsign.InputFile = "input.pdf";
pdfsign.OutputFile = "signed.pdf";
pdfsign.SigningCert = new Certificate(CertStoreTypes.cstPFXFile, "cert.pfx", "password", "*");
pdfsign.SignatureProfile = PDFSignSignatureProfiles.pfBaselineT;
pdfsign.TimestampServer = "http://time.certum.pl";
pdfsign.ValidationPolicy = PDFSignValidationPolicies.vpNone;
pdfsign.Sign();
```

 **PAdES B-LTA**

The PAdES B-LTA profile is used to achieve signatures that are equipped with long-term archival (LTA) or long-term validation (LTV) capabilities. It incorporates into the signature all the material required to validate the signature, including signing certificates, timestamping certificates, and revocation information. It also adds a document timestamp, which certifies the integrity of both the document and the complete validation material at a specific moment in time. This guarantees that no relevant certificates were expired or revoked at the signature creation time, and enables the signature to be verified offline.

Creating a B-LTA signature with PDFSign is a two-step process. First [Sign](#sign-method-pdfsign-component) the document and add a signature timestamp, setting [SignatureProfile](#signatureprofile-property-pdfsign-component) appropriately. Then [Update](#update-method-pdfsign-component) the signature to take care of the rest (collect and embed the validation material, and add a document timestamp):

```csharp
pdfsign.InputFile = "input.pdf";
pdfsign.OutputFile = "signed.pdf";
pdfsign.SigningCert = new Certificate(CertStoreTypes.cstPFXFile, "cert.pfx", "password", "*");
pdfsign.SignatureProfile = PDFSignSignatureProfiles.pfBaselineT;
pdfsign.TimestampServer = "http://time.certum.pl";
pdfsign.ValidationPolicy = PDFSignValidationPolicies.vpNone;
pdfsign.Sign();

// Update the signature to LTV - this retrieves the necessary revocation
// elements, embeds them into the document, and adds a document timestamp
pdfsign.Reset();
pdfsign.InputFile = "signed.pdf";
pdfsign.OutputFile = "updated.pdf";
pdfsign.TimestampServer = "http://time.certum.pl";
pdfsign.Update();
```

 Validation material "completeness" can be subjective and depends on several factors, including the following:

- The working environment. For example, your organization may explicitly trust its own self-signed TSA certificate. Signatures timestamped with this certificate will be considered B-LTA by your organization, but for any external bodies, those signatures would be rendered as B-LT or even B-B, as they do not know or trust the custom TSA certificate.
- The time that has passed since the last document timestamp. If an archived (B-LTA) document is not re-timestamped before its last timestamp expires, it will drop back to a lower signature level.

### Chain Validation Setup

 Chain validation is a sophisticated, multifaceted procedure that involves a lot of variables. Depending on the configuration of your operating environment, the specifics of the PKI framework being used, and the validation policy you need to follow, you may want to adjust your chain validation parameters to best fit your requirements. A summary of these parameters is given below.

NOTE: These parameters apply to [Sign](#sign-method-pdfsign-component) and [Update](#update-method-pdfsign-component) in PDFSign as well as [Verify](PDFVerify.md#PDFVerify_m_Verify) in PDFVerify, as all three methods execute the chain validation procedure (if it is enabled).

**Validation Policy**

The [ValidationPolicy](#validationpolicy-property-pdfsign-component) property dictates how thoroughly the chain is validated. It includes options to control which checks the component performs, allowing you to tailor the validation process to meet your specific security needs. For example, if it is not essential to check each certificate's revocation status, set this property to *vpFullNoRevocation*.

**Revocation**

The revocation aspect of chain validation is controlled by the [RevocationCheck](#revocationcheck-property-pdfsign-component) property, which allows you to choose between and prioritize revocation origins.

NOTE: OCSP sources are often preferred to CRL endpoints because of their real-time capability and the smaller size of the responses they produce.

**Trust**

The trust aspect of chain validation is controlled by the [TrustSources](#trustsources-property-pdfsign-component) property, which allows you to specify the locations in which the component searches for trust anchors. Local system stores, your own trusted root certificates (through the [TrustedCerts](#trustedcerts-property-pdfsign-component) property), and Trusted Lists (through the [TrustedLists](#trustedlists-property-pdfsign-component) property) are all supported.

**Offline Mode**

The [OfflineMode](#offlinemode-property-pdfsign-component) property provides the ability to sign or verify the document without contacting online sources. If this property is enabled, the component only uses [KnownCerts](#knowncerts-property-pdfsign-component), [TrustedCerts](#trustedcerts-property-pdfsign-component), data structures within the document, and revocation and Trusted List data that it previously saved to its internal cache when looking for missing validation material.

## Property List

*The following is the full list of the properties of the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [Attachments](#attachments-property-pdfsign-component) | A collection of all attached files found in the document. |
| [BlockedCerts](#blockedcerts-property-pdfsign-component) | The certificates that must be rejected as trust anchors. |
| [DecryptionCert](#decryptioncert-property-pdfsign-component) | The decryption certificate. |
| [DocumentCerts](#documentcerts-property-pdfsign-component) | A collection of certificates read from the document during processing. |
| [Firewall](#firewall-property-pdfsign-component) | A set of properties related to firewall access. |
| [InputData](#inputdata-property-pdfsign-component) | A byte array containing the PDF document to process. |
| [InputFile](#inputfile-property-pdfsign-component) | The PDF file to process. |
| [KnownCerts](#knowncerts-property-pdfsign-component) | A collection of additional certificates for chain validation. |
| [OfflineMode](#offlinemode-property-pdfsign-component) | Whether the component is operating in offline mode. |
| [OutputData](#outputdata-property-pdfsign-component) | A byte array containing the PDF document after processing. |
| [OutputFile](#outputfile-property-pdfsign-component) | The path to a local file where the output is written. |
| [Overwrite](#overwrite-property-pdfsign-component) | Whether the component should overwrite files. |
| [Password](#password-property-pdfsign-component) | The password to decrypt the document with. |
| [Proxy](#proxy-property-pdfsign-component) | A set of properties related to proxy access. |
| [RemoteSignatureData](#remotesignaturedata-property-pdfsign-component) | The signature data obtained from a remote signer. |
| [RemoteSignatureDigest](#remotesignaturedigest-property-pdfsign-component) | The digest to be signed remotely. |
| [RemoteSignatureMethod](#remotesignaturemethod-property-pdfsign-component) | The remote signing method. |
| [RevocationCheck](#revocationcheck-property-pdfsign-component) | The kind(s) of revocation check to perform for all chain certificates. |
| [SignatureAuthorName](#signatureauthorname-property-pdfsign-component) | The human-readable name of the signer. |
| [SignatureClaimedSigningTime](#signatureclaimedsigningtime-property-pdfsign-component) | The signature's creation time. |
| [SignatureField](#signaturefield-property-pdfsign-component) | The index of the empty signature field to sign. |
| [SignatureHashAlgorithm](#signaturehashalgorithm-property-pdfsign-component) | The hash algorithm to be used for signing. |
| [SignatureProfile](#signatureprofile-property-pdfsign-component) | The PAdES profile to apply when creating the signature. |
| [SignatureReason](#signaturereason-property-pdfsign-component) | The reason for signing. |
| [Signatures](#signatures-property-pdfsign-component) | A collection of all the signatures and empty fields found in the document. |
| [SignatureType](#signaturetype-property-pdfsign-component) | The type of signature to create. |
| [SignatureWidgetHeight](#signaturewidgetheight-property-pdfsign-component) | The height of the signature widget. |
| [SignatureWidgetOffsetX](#signaturewidgetoffsetx-property-pdfsign-component) | The signature widget offset from the left-hand page border. |
| [SignatureWidgetOffsetY](#signaturewidgetoffsety-property-pdfsign-component) | The signature widget offset from the bottom page border. |
| [SignatureWidgetPages](#signaturewidgetpages-property-pdfsign-component) | The pages to place the signature and its widget on. |
| [SignatureWidgetWidth](#signaturewidgetwidth-property-pdfsign-component) | The width of the signature widget. |
| [SigningCert](#signingcert-property-pdfsign-component) | The certificate to be used for signing. |
| [TimestampServer](#timestampserver-property-pdfsign-component) | The address of the timestamping server. |
| [TrustedCerts](#trustedcerts-property-pdfsign-component) | A collection of trusted certificates for chain validation. |
| [TrustedLists](#trustedlists-property-pdfsign-component) | A list of known Trusted Lists for chain validation. |
| [TrustSources](#trustsources-property-pdfsign-component) | The trust sources to use during chain validation. |
| [ValidationFlags](#validationflags-property-pdfsign-component) | Additional chain validation settings. |
| [ValidationPolicy](#validationpolicy-property-pdfsign-component) | The level at which to perform chain validation. |
| [ValidationTime](#validationtime-property-pdfsign-component) | The time point at which the signature should be validated. |

## Method List

*The following is the full list of the methods of the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [AddAttachment](#addattachment-method-pdfsign-component) | Adds an attachment to the document. |
| [AddTimestamp](#addtimestamp-method-pdfsign-component) | Adds a document timestamp to the document. |
| [Close](#close-method-pdfsign-component) | Closes the opened document. |
| [Config](#config-method-pdfsign-component) | Sets or retrieves a configuration setting. |
| [Encrypted](#encrypted-method-pdfsign-component) | Checks whether the document is encrypted. |
| [GetPageProperty](#getpageproperty-method-pdfsign-component) | Returns the value of a page property. |
| [GetWidgetProperty](#getwidgetproperty-method-pdfsign-component) | Returns the value of a signature widget property. |
| [Interrupt](#interrupt-method-pdfsign-component) | Interrupts the current action. |
| [Open](#open-method-pdfsign-component) | Opens the document for processing. |
| [RemoveAttachment](#removeattachment-method-pdfsign-component) | Removes an attachment from the document. |
| [Reset](#reset-method-pdfsign-component) | Resets the component. |
| [SaveAttachment](#saveattachment-method-pdfsign-component) | Saves a PDF attachment to a file. |
| [SetInputStream](#setinputstream-method-pdfsign-component) | Sets the stream containing the PDF document to process. |
| [SetOutputStream](#setoutputstream-method-pdfsign-component) | Sets the stream to write the processed document to. |
| [SetWidgetProperty](#setwidgetproperty-method-pdfsign-component) | Sets the value of a signature widget property. |
| [Sign](#sign-method-pdfsign-component) | Signs the data. |
| [Signed](#signed-method-pdfsign-component) | Checks whether the document is signed. |
| [Update](#update-method-pdfsign-component) | Updates the most recent signature. |

## Event List

*The following is the full list of the events fired by the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [ChainCert](#chaincert-event-pdfsign-component) | Fired when the component encounters a chain certificate. |
| [DocumentInfo](#documentinfo-event-pdfsign-component) | Fired when the document has been loaded into memory. |
| [Error](#error-event-pdfsign-component) | Fired when information is available about errors during data delivery. |
| [Log](#log-event-pdfsign-component) | Fired once for each log message. |
| [Password](#password-event-pdfsign-component) | Fired when the component detects that the document is encrypted with a password. |
| [RecipientInfo](#recipientinfo-event-pdfsign-component) | Fired for each recipient certificate of the encrypted document. |
| [SignatureInfo](#signatureinfo-event-pdfsign-component) | Fired when the component finds a signature in the document. |
| [SignatureProcessed](#signatureprocessed-event-pdfsign-component) | Fired after a signature has been processed. |
| [SSLServerAuthentication](#sslserverauthentication-event-pdfsign-component) | Fired after the server presents its certificate to the client. |
| [SSLStatus](#sslstatus-event-pdfsign-component) | Fired when secure connection progress messages are available. |

## Config Settings

*The following is a list of config settings for the component with short descriptions. Click on the links for further details.*

|  |  |
| --- | --- |
| [AFRelationship\[Key\]](#AFRelationship[Key]) | The value of the AFRelationship key for the attachment. |
| [CacheRevocationInfo](#CacheRevocationInfo) | Whether to cache revocation information. |
| [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) | Whether to close the input stream after processing. |
| [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing) | Whether to close the output stream after processing. |
| [CompressDSS](#CompressDSS) | Whether to compress content in the DSS dictionary. |
| [ContactInfo\[Index\]](#ContactInfo[Index]) | The signer's contact information. |
| [CustomProfile](#CustomProfile) | A pre-defined custom profile to apply when creating the signature. |
| [CustomSignedAttributes](#CustomSignedAttributes) | The custom signed attributes to be added to the inner CMS. |
| [EnforcePDFA](#EnforcePDFA) | Whether to enforce PDF/A compliance. |
| [ExtraSpace](#ExtraSpace) | The number of extra zero bytes to allocate in the document behind the signature. |
| [FallbackFont](#FallbackFont) | The fallback font. |
| [FilterName\[Index\]](#FilterName[Index]) | The signature filter name. |
| [FontPaths](#FontPaths) | The font search paths. |
| [FullSignatureName\[Index\]](#FullSignatureName[Index]) | The full name of the signature field. |
| [HTTPRetryCount](#HTTPRetryCount) | The number of HTTP request retries. |
| [HTTPRetryInterval](#HTTPRetryInterval) | A time interval to apply between HTTP request retries. |
| [IncludeRevocationInfo](#IncludeRevocationInfo) | Whether to include revocation information in the document. |
| [IncludeSigningChain](#IncludeSigningChain) | Whether to include the full signing chain in the signature. |
| [LogLevel](#LogLevel) | The level of detail that is logged. |
| [OwnerPassword](#OwnerPassword) | The owner password to decrypt the document with. |
| [PDFALevel](#PDFALevel) | The PDF/A conformance level to enforce. |
| [PDFAPolicy](#PDFAPolicy) | The PDF/A policy to follow. |
| [Permissions](#Permissions) | The document permissions associated with the encryption. |
| [PolicyHash](#PolicyHash) | The signature policy hash value. |
| [PolicyHashAlgorithm](#PolicyHashAlgorithm) | The algorithm that was used to calculate the signature policy hash. |
| [PolicyId](#PolicyId) | The policy Id to be included in the signature. |
| [PreferEmbeddedRevocationInfo](#PreferEmbeddedRevocationInfo) | Whether to prioritize revocation information that is embedded into the document. |
| [RemoteSignatureData](#RemoteSignatureData) | The hex-encoded signature data obtained from a remote signing engine. |
| [RemoteSignatureDigest](#RemoteSignatureDigest) | The hex-encoded digest to be signed remotely. |
| [RemoteSignatureMethod](#RemoteSignatureMethod) | The remote signing method. |
| [RevisionOffsets](#RevisionOffsets) | The offsets of the document revisions. |
| [SaveChanges](#SaveChanges) | Whether to save changes made to the document. |
| [SignatureData\[Index\]](#SignatureData[Index]) | The hex-encoded representation of the underlying PKCS#7/CMS signature container. |
| [SystemFontNames](#SystemFontNames) | The system font names. |
| [TempPath](#TempPath) | The location where temporary files are stored. |
| [TimestampHashAlgorithm](#TimestampHashAlgorithm) | A specific hash algorithm for use with the timestamping service. |
| [TSATLSClientCertStore](#TSATLSClientCertStore) | The TLS client certificate store to search. |
| [TSATLSClientCertStorePassword](#TSATLSClientCertStorePassword) | The password needed to open the TLS client certificate store. |
| [TSATLSClientCertStoreType](#TSATLSClientCertStoreType) | The type of the TLS client certificate store. |
| [TSATLSClientCertSubject](#TSATLSClientCertSubject) | The subject of the TLS client certificate. |
| [UpdateIndex](#UpdateIndex) | The index of the signature to update. |
| [UsePSS](#UsePSS) | Whether to use RSA-PSS during signing and verification. |
| [BuildInfo](#BuildInfo) | Information about the product's build. |
| [GUIAvailable](#GUIAvailable) | Whether or not a message loop is available for processing events. |
| [LicenseInfo](#LicenseInfo) | Information about the current license. |
| [MaskSensitiveData](#MaskSensitiveData) | Whether sensitive data is masked in log messages. |
| [UseInternalSecurityAPI](#UseInternalSecurityAPI) | Whether or not to use the system security libraries or an internal implementation. |

# Attachments Property ([PDFSign](#pdfsign-component) Component)

A collection of all attached files found in the document.

## Syntax

```text
public PDFAttachmentList Attachments { get; }
```

## Remarks

This property is used to access the details of all the attached files identified in the document. Use [AddAttachment](#addattachment-method-pdfsign-component), [RemoveAttachment](#removeattachment-method-pdfsign-component), and [SaveAttachment](#saveattachment-method-pdfsign-component) to add, remove, and save attachments to/from this collection respectively.

This property is not available at design time.

 Please refer to the [PDFAttachment](#pdfattachment-type) type for a complete list of fields.

# BlockedCerts Property ([PDFSign](#pdfsign-component) Component)

The certificates that must be rejected as trust anchors.

## Syntax

```text
public CertificateList BlockedCerts { get; }
```

## Remarks

This property is used to supply a list of compromised or blocked certificates to the component. Note that any chain containing a blocked certificate will fail validation.

This property is not available at design time.

 Please refer to the [Certificate](#certificate-type) type for a complete list of fields.

# DecryptionCert Property ([PDFSign](#pdfsign-component) Component)

The decryption certificate.

## Syntax

```text
public Certificate DecryptionCert { get; set; }
```

## Remarks

This property is used to provide the certificate used for decryption. Note that this certificate must have a private key associated with it.

This property is not available at design time.

 Please refer to the [Certificate](#certificate-type) type for a complete list of fields.

# DocumentCerts Property ([PDFSign](#pdfsign-component) Component)

A collection of certificates read from the document during processing.

## Syntax

```text
public CertificateList DocumentCerts { get; }
```

## Remarks

This property is used to access all certificates encountered during document processing and embedded into the signature(s). When signing or verifying, this collection is populated automatically during chain validation.

This property is read-only and not available at design time.

 Please refer to the [Certificate](#certificate-type) type for a complete list of fields.

# Firewall Property ([PDFSign](#pdfsign-component) Component)

A set of properties related to firewall access.

## Syntax

```text
public Firewall Firewall { get; set; }
```

## Remarks

This is a [Firewall](#firewall-type)-type property, which contains fields describing the firewall through which the component will attempt to connect.

 Please refer to the [Firewall](#firewall-type) type for a complete list of fields.

# InputData Property ([PDFSign](#pdfsign-component) Component)

A byte array containing the PDF document to process.

## Syntax

```text
public byte[] InputData { get; set; }
```

## Remarks

This property is used to assign a byte array containing the PDF document to be processed.

This property is not available at design time.

# InputFile Property ([PDFSign](#pdfsign-component) Component)

The PDF file to process.

## Syntax

```text
public string InputFile { get; set; }
```

## Default Value

""

## Remarks

This property is used to provide a path to the PDF document to be processed.

# KnownCerts Property ([PDFSign](#pdfsign-component) Component)

A collection of additional certificates for chain validation.

## Syntax

```text
public CertificateList KnownCerts { get; }
```

## Remarks

This property is used to supply a list of additional certificates to the component that might be needed for chain validation. For instance, intermediary CA certificates may be absent from the standard system locations (or there may be no standard system locations) and therefore should be supplied to the component manually.

The purpose of this certificate collection is roughly equivalent to that of the Intermediate Certification Authorities system store in Windows.

NOTE: Do not add trust anchors or root certificates to this collection; add them to [TrustedCerts](#trustedcerts-property-pdfsign-component) instead.

This property is not available at design time.

 Please refer to the [Certificate](#certificate-type) type for a complete list of fields.

# OfflineMode Property ([PDFSign](#pdfsign-component) Component)

Whether the component is operating in offline mode.

## Syntax

```text
public bool OfflineMode { get; set; }
```

## Default Value

False

## Remarks

This property indicates whether the component should operate in offline mode.

In offline mode, the component restricts itself from accessing online Trusted Lists and revocation information sources such as CRLs or OCSP responders. It may be useful to set this property to *true* if there is a need to verify the completeness of the validation information included within the signature or provided via [KnownCerts](#knowncerts-property-pdfsign-component).

# OutputData Property ([PDFSign](#pdfsign-component) Component)

A byte array containing the PDF document after processing.

## Syntax

```text
public byte[] OutputData { get; }
```

## Remarks

This property is used to read the byte array containing the produced output after the operation has completed. It is only set if an output file and output stream have not been assigned via [OutputFile](#outputfile-property-pdfsign-component) and [SetOutputStream](#setoutputstream-method-pdfsign-component) respectively.

This property is read-only and not available at design time.

# OutputFile Property ([PDFSign](#pdfsign-component) Component)

The path to a local file where the output is written.

## Syntax

```text
public string OutputFile { get; set; }
```

## Default Value

""

## Remarks

This property is used to provide a path where the resulting PDF document is saved after the operation has completed.

# Overwrite Property ([PDFSign](#pdfsign-component) Component)

Whether the component should overwrite files.

## Syntax

```text
public bool Overwrite { get; set; }
```

## Default Value

False

## Remarks

This property indicates whether the component overwrites [OutputFile](#outputfile-property-pdfsign-component). If set to *false*, an error is thrown whenever [OutputFile](#outputfile-property-pdfsign-component) exists before an operation.

# Password Property ([PDFSign](#pdfsign-component) Component)

The password to decrypt the document with.

## Syntax

```text
public string Password { get; set; }
```

## Default Value

""

## Remarks

This property is used to provide the user password for decryption. Though it may be different from [OwnerPassword](#OwnerPassword), most implementations use the same value for both.

# Proxy Property ([PDFSign](#pdfsign-component) Component)

A set of properties related to proxy access.

## Syntax

```text
public Proxy Proxy { get; set; }
```

## Remarks

This property contains fields describing the proxy through which the component will attempt to connect.

 Please refer to the [Proxy](#proxy-type) type for a complete list of fields.

# RemoteSignatureData Property ([PDFSign](#pdfsign-component) Component)

The signature data obtained from a remote signer.

## Syntax

```text
public string RemoteSignatureData { get; set; }
```

## Default Value

""

## Remarks

This property is used to specify the hex-encoded signature data obtained from a remote signer. Use it to pass the [RemoteSignatureDigest](#remotesignaturedigest-property-pdfsign-component) back to the component (after it has been processed appropriately and signed) to complete the signature.

# RemoteSignatureDigest Property ([PDFSign](#pdfsign-component) Component)

The digest to be signed remotely.

## Syntax

```text
public string RemoteSignatureDigest { get; }
```

## Default Value

""

## Remarks

This property is used to read the hex-encoded digest that should be passed to a remote signer to be signed. Note that in the PKCS#1 method, this value is the raw data of the PKCS#7 signed-attributes field, whereas in the PKCS#7 method, it is the document hash.

This property is read-only.

# RemoteSignatureMethod Property ([PDFSign](#pdfsign-component) Component)

The remote signing method.

## Syntax

```text
public PDFSignRemoteSignatureMethods RemoteSignatureMethod { get; set; }
enum PDFSignRemoteSignatureMethods {
  rsmNone,
  rsmPKCS1,
  rsmPKCS7,
  rsmDigest,
  rsmBlob
}
```

## Default Value

0

## Remarks

This property is used to specify whether and how the new signature is intended to be created remotely. If set to *rsmPKCS1*, *rsmPKCS7*, or *rsmBlob* before [Sign](#sign-method-pdfsign-component) is called, the component does not perform the low-level signing operation itself but instead delegates it to an external or remote signer.

Possible values are:

|  |  |
| --- | --- |
| 0 (rsmNone - default) | Do not create the signature remotely. |
| 1 (rsmPKCS1) | Create the signature remotely using the PKCS#1 signing method. The component builds the PKCS#7 structure itself and populates [RemoteSignatureDigest](#remotesignaturedigest-property-pdfsign-component) with the raw data of the signed-attributes field. Note that [SigningCert](#signingcert-property-pdfsign-component) must be set in order to use this option. |
| 2 (rsmPKCS7) | Create the signature remotely using the PKCS#7 signing method. The component populates [RemoteSignatureDigest](#remotesignaturedigest-property-pdfsign-component) with the document hash, and the remote signer is expected to build the PKCS#7 structure. Use this option if the signing certificate is not available. |
| 3 (rsmDigest) | Sign the digest generated earlier using the PKCS#7 method and produce the corresponding PKCS#7 structure. The input is expected to contain an unencoded binary message digest, and the output is a binary PKCS#7 object. Unlike the other options, this is a one-pass method. Note that no PDF data is involved in either input or output. |
| 4 (rsmBlob) | Create the signature remotely given the digest generated earlier using the PKCS#7 method. The input is expected to contain an unencoded binary message digest, and the component builds the PKCS#7 structure and outputs the raw data of the signed-attributes field. This data is expected to be signed with the respective private key and passed back to the component to complete the PKCS#7 structure. Note that [SigningCert](#signingcert-property-pdfsign-component) must be set in order to use this option, and no PDF data is involved in either input or output. |

# RevocationCheck Property ([PDFSign](#pdfsign-component) Component)

The kind(s) of revocation check to perform for all chain certificates.

## Syntax

```text
public PDFSignRevocationChecks RevocationCheck { get; set; }
enum PDFSignRevocationChecks {
  rcAllCRL,
  rcAllOCSP,
  rcAllCRLAndOCSP,
  rcAnyCRL,
  rcAnyOCSP,
  rcAnyCRLOrOCSP,
  rcAnyOCSPOrCRL
}
```

## Default Value

6

## Remarks

This property is used to specify the revocation sources and preferences the component uses during chain validation. Revocation checking is necessary to ensure the integrity of the chain and to obtain up-to-date certificate validity and trust information.

Certificate Revocation Lists (CRLs) and Online Certificate Status Protocol (OCSP) responses serve the same purpose of ensuring that the certificate has not been revoked by the Certificate Authority (CA) at the time of use. Depending on the circumstances and security policy requirements, either one or both of the revocation information source types may be used.

Possible values are:

|  |  |
| --- | --- |
| 0 (rcAllCRL) | All provided CRL endpoints are checked, and all checks must succeed. |
| 1 (rcAllOCSP) | All provided OCSP endpoints are checked, and all checks must succeed. |
| 2 (rcAllCRLAndOCSP) | All provided CRL and OCSP endpoints are checked, and all checks must succeed. |
| 3 (rcAnyCRL) | All provided CRL endpoints are checked, and at least one check must succeed. |
| 4 (rcAnyOCSP) | All provided OCSP endpoints are checked, and at least one check must succeed. |
| 5 (rcAnyCRLOrOCSP) | All provided CRL and OCSP endpoints are checked, and at least one check must succeed. CRL endpoints are checked first. |
| 6 (rcAnyOCSPOrCRL - default) | All provided CRL and OCSP endpoints are checked, and at least one check must succeed. OCSP endpoints are checked first. |

This property controls the way revocation checks are performed for every certificate in the chain. Typically, certificates come with two types of revocation information sources: CRLs (Certificate Revocation Lists) and OCSP responses. CRLs are static objects periodically published by the CA at some online location. OCSP responders are active online services maintained by the CA that can provide up-to-date information on certificate statuses in near real time.

There are some conceptual differences between the two. CRLs are normally larger in size. Their use involves some latency because there is normally a delay between the time at which a certificate was revoked and the time at which the subsequent CRL mentioning that revocation is published. The benefits of CRLs are that the same object can provide statuses for all certificates issued by a particular CA, and that the whole technology is much simpler than OCSP (and thus is supported by more CAs).

This property allows the validation course to be adjusted by including or excluding certain types of revocation sources from the validation process. The *rcAnyOCSPOrCRL* setting (give preference to the faster OCSP route and only demand one source to succeed) is a good choice for most typical validation environments. The *rcAll** modes are much stricter, and may be used in scenarios where bulletproof validity information is essential.

NOTE: If no CRL or OCSP endpoints are provided by the CA, the revocation check is considered successful. This is because the CA chose not to supply revocation information for its certificates, meaning they are considered irrevocable.

NOTE: Within each of the above settings, if any retrieved CRL or OCSP response indicates that the certificate has been revoked, the revocation check fails.

# SignatureAuthorName Property ([PDFSign](#pdfsign-component) Component)

The human-readable name of the signer.

## Syntax

```text
public string SignatureAuthorName { get; set; }
```

## Default Value

""

## Remarks

This property is used to specify the human-readable name of the signer.

NOTE: This property only applies when creating a new signature.

# SignatureClaimedSigningTime Property ([PDFSign](#pdfsign-component) Component)

The signature's creation time.

## Syntax

```text
public string SignatureClaimedSigningTime { get; set; }
```

## Default Value

""

## Remarks

This property is used to specify the signature creation time from the signer's computer. The time should be provided in UTC in *yyyyMMddHHmmssZ* format.

If this property is empty when a new signature is created, the component uses the current UTC time.

NOTE: This property only applies when creating a new signature.

# SignatureField Property ([PDFSign](#pdfsign-component) Component)

The index of the empty signature field to sign.

## Syntax

```text
public int SignatureField { get; set; }
```

## Default Value

-1

## Remarks

This property is used to specify the empty signature field that should be signed. If the default value of *-1* is assigned to this property, a new signature field is created.

**Example:**

```csharp
pdfsign.InputFile = "input.pdf";
pdfsign.OutputFile = "emptyfield.pdf";
pdfsign.SignatureType = PDFSignSignatureTypes.stEmptyField;
pdfsign.Sign();
// Later
pdfsign.Reset();
pdfsign.InputFile = "emptyfield.pdf";
pdfsign.OutputFile = "signed.pdf";
pdfsign.SigningCert = new Certificate(CertStoreTypes.cstPFXFile, "cert.pfx", "password", "*");
pdfsign.SignatureField = 0;
// Configure signature properties as desired
pdfsign.Sign();
```

# SignatureHashAlgorithm Property ([PDFSign](#pdfsign-component) Component)

The hash algorithm to be used for signing.

## Syntax

```text
public string SignatureHashAlgorithm { get; set; }
```

## Default Value

"SHA256"

## Remarks

This property is used to specify the hash algorithm to be used for signing.

Possible values are:

- SHA1
- SHA224
- SHA256
- SHA384
- SHA512
- MD5

 NOTE: This property only applies when creating a new signature.

# SignatureProfile Property ([PDFSign](#pdfsign-component) Component)

The PAdES profile to apply when creating the signature.

## Syntax

```text
public PDFSignSignatureProfiles SignatureProfile { get; set; }
enum PDFSignSignatureProfiles {
  pfNone,
  pfBaselineB,
  pfBaselineT,
  pfBaselineLT,
  pfBaselineLTA
}
```

## Default Value

0

## Remarks

This property is used to specify a pre-defined PAdES profile to apply when creating the signature, as defined by ETSI.

Advanced signatures come in many variants, and they are often defined by parties that need to process them or by local standards. Profiles are sets of pre-defined configurations that correspond to particular signature variants. Specifying a profile pre-configures the component to make it produce the signature that matches the configuration corresponding to that profile.

Possible values are:

|  |  |
| --- | --- |
| 0 (pfNone - default) | No profile |
| 1 (pfBaselineB) | PAdES B-B profile |
| 2 (pfBaselineT) | PAdES B-T profile |
| 3 (pfBaselineLT) | PAdES B-LT profile |
| 4 (pfBaselineLTA) | PAdES B-LTA profile |

To apply a custom profile that is not defined by ETSI, set [CustomProfile](#CustomProfile).

NOTE: This property only applies when creating a new signature.

# SignatureReason Property ([PDFSign](#pdfsign-component) Component)

The reason for signing.

## Syntax

```text
public string SignatureReason { get; set; }
```

## Default Value

""

## Remarks

This property is used to specify the reason for signing.

NOTE: This property only applies when creating a new signature.

# Signatures Property ([PDFSign](#pdfsign-component) Component)

A collection of all the signatures and empty fields found in the document.

## Syntax

```text
public PDFSignatureList Signatures { get; }
```

## Remarks

This property is used to access the details of all the signatures and empty signature fields identified in the document.

This property is read-only and not available at design time.

 Please refer to the [PDFSignature](#pdfsignature-type) type for a complete list of fields.

# SignatureType Property ([PDFSign](#pdfsign-component) Component)

The type of signature to create.

## Syntax

```text
public PDFSignSignatureTypes SignatureType { get; set; }
enum PDFSignSignatureTypes {
  stLegacy,
  stAdvanced,
  stDTS,
  stEmptyField
}
```

## Default Value

0

## Remarks

This property is used to specify the type of the signature. For PAdES signatures, use [SignatureProfile](#signatureprofile-property-pdfsign-component) to specify the PAdES profile.

Possible values are:

|  |  |
| --- | --- |
| 0 (stLegacy - default) | Legacy Adobe signature (adbe.pkcs7.detached) |
| 1 (stAdvanced) | PAdES-compliant signature (ETSI.CAdES.detached) |
| 2 (stDTS) | Document timestamp (ETSI.RFC3161) |
| 3 (stEmptyField) | Empty signature field (signature placeholder) |

NOTE: This property only applies when creating a new signature.

# SignatureWidgetHeight Property ([PDFSign](#pdfsign-component) Component)

The height of the signature widget.

## Syntax

```text
public string SignatureWidgetHeight { get; set; }
```

## Default Value

"70"

## Remarks

This property is used to specify the height of the signature widget in points. Both integer and decimal values are supported.

NOTE: This property only applies when creating a new signature.

# SignatureWidgetOffsetX Property ([PDFSign](#pdfsign-component) Component)

The signature widget offset from the left-hand page border.

## Syntax

```text
public string SignatureWidgetOffsetX { get; set; }
```

## Default Value

"0"

## Remarks

This property is used to specify the signature widget offset from the left-hand page border in points. Both integer and decimal values are supported.

NOTE: This property only applies when creating a new signature.

# SignatureWidgetOffsetY Property ([PDFSign](#pdfsign-component) Component)

The signature widget offset from the bottom page border.

## Syntax

```text
public string SignatureWidgetOffsetY { get; set; }
```

## Default Value

"0"

## Remarks

This property is used to specify the signature widget offset from the bottom page border in points. Both integer and decimal values are supported.

NOTE: This property only applies when creating a new signature.

# SignatureWidgetPages Property ([PDFSign](#pdfsign-component) Component)

The pages to place the signature and its widget on.

## Syntax

```text
public string SignatureWidgetPages { get; set; }
```

## Default Value

""

## Remarks

This property is used to specify the pages on which the signature and its widget are placed.

A variety of syntaxes are supported:

- A single page index (zero-based): *3*
- A comma-separated list of page indices (zero-based): *1,2,5,7*
- The asterisk character (***) indicates that the widget should be placed on all pages in the document.
- The *first* and *last* placeholders specify that the signature should be placed on the respective page, independently of its number.

 NOTE: If no valid pages are specified, the component places the widget on the first page by default.

NOTE: This property only applies when creating a new signature.

# SignatureWidgetWidth Property ([PDFSign](#pdfsign-component) Component)

The width of the signature widget.

## Syntax

```text
public string SignatureWidgetWidth { get; set; }
```

## Default Value

"70"

## Remarks

This property is used to specify the width of the signature widget in points. Both integer and decimal values are supported.

NOTE: This property only applies when creating a new signature.

# SigningCert Property ([PDFSign](#pdfsign-component) Component)

The certificate to be used for signing.

## Syntax

```text
public Certificate SigningCert { get; set; }
```

## Remarks

This property is used to provide the certificate used for signing. Note that this certificate must have a private key associated with it, unless PKCS#1 remote signing is being used. This property must be set if [RemoteSignatureMethod](#remotesignaturemethod-property-pdfsign-component) is set to *rsmNone*, *rsmPKCS1*, or *rsmDigest*.

This property is not available at design time.

 Please refer to the [Certificate](#certificate-type) type for a complete list of fields.

# TimestampServer Property ([PDFSign](#pdfsign-component) Component)

The address of the timestamping server.

## Syntax

```text
public string TimestampServer { get; set; }
```

## Default Value

""

## Remarks

This property is used to specify the address of the TSA (Timestamping Authority) server to use for timestamping the signature (normal signing) or the document (LTV update).

If the timestamping service enforces credential-based user authentication (basic or digest), the credentials can be provided in the same URL. For example:

```csharp
pdfsign.TimestampServer = "http://user:password@timestamp.server.com/TsaService";
```

 If the TSA requires TLS client authentication, provide the client certificate via [TSATLSClientCertStoreType](#TSATLSClientCertStoreType), [TSATLSClientCertStore](#TSATLSClientCertStore), [TSATLSClientCertStorePassword](#TSATLSClientCertStorePassword), and [TSATLSClientCertSubject](#TSATLSClientCertSubject).

# TrustedCerts Property ([PDFSign](#pdfsign-component) Component)

A collection of trusted certificates for chain validation.

## Syntax

```text
public CertificateList TrustedCerts { get; }
```

## Remarks

This property is used to supply a list of trusted certificates to the component that might be needed for chain validation. For instance, root CA certificates may be absent from the standard system locations (or there may be no standard system locations) and therefore should be supplied to the component manually.

The purpose of this certificate collection is largely the same as that of the Windows Trusted Root Certification Authorities system store.

Use this property with extreme care as it directly affects chain verifiability; a wrong certificate added to the list of trusted certificates may result in bad chains being accepted and forged signatures being recognized as genuine. Only add certificates that originate from parties that are known and trusted.

This property is not available at design time.

 Please refer to the [Certificate](#certificate-type) type for a complete list of fields.

# TrustedLists Property ([PDFSign](#pdfsign-component) Component)

A list of known Trusted Lists for chain validation.

## Syntax

```text
public string TrustedLists { get; set; }
```

## Default Value

"%EUTL%"

## Remarks

This property is used to supply a semicolon-separated list of URLs or paths of known Trusted Lists to the component for chain validation.

A Trusted List is an XML document that contains a government-issued list of CAs that have passed regulated compliance checks. When validating the chain, the component consults the Trusted List to establish certificate trust, ensuring that the CA is legitimate and entitled to issue certificates of the kind being checked.

The default value is the special *%EUTL%* macro, which, if applicable, instructs the component to check the root certificate against up-to-date versions of the primary EU Trusted Lists from the [EU LOTL](https://ec.europa.eu/tools/lotl/eu-lotl.xml). Custom values can be appended:

```csharp
component.TrustedLists = "%EUTL%;http://my.company/tsl;c:\tsls\mytsl.xml";
```

 NOTE: The component caches all Trusted Lists it downloads and uses during chain validation. This cache is shared between component instances within the same process. If this property contains a URL that is also present in the cache, the component retrieves the cached data and reuses it in the current validation. If the data is invalid, the component downloads a fresh Trusted List and adds it to the cache.

# TrustSources Property ([PDFSign](#pdfsign-component) Component)

The trust sources to use during chain validation.

## Syntax

```text
public PDFSignTrustSources TrustSources { get; set; }
enum PDFSignTrustSources {
  tsManual,
  tsLocal,
  tsTrustedLists,
  tsLocalAndTrustedLists
}
```

## Default Value

3

## Remarks

This property is used to specify the sources the component uses to establish certificate trust during chain validation.

Establishing trust for a particular certificate, when either signing or verifying, involves building a chain up to a valid trust anchor. This trust anchor is a root certificate that typically resides on the local system. If the certificate does not eventually chain up to a valid trust anchor, the chain is considered untrusted and therefore invalid.

Possible values are:

|  |  |
| --- | --- |
| 0 (tsManual) | The component consults [TrustedCerts](#trustedcerts-property-pdfsign-component) only. |
| 1 (tsLocal) | The component consults local system stores (e.g., Windows Trusted Root Certification Authorities) as well as [TrustedCerts](#trustedcerts-property-pdfsign-component). |
| 2 (tsTrustedLists) | The component consults [TrustedLists](#trustedlists-property-pdfsign-component) only. |
| 3 (tsLocalAndTrustedLists - default) | The component consults local system stores, [TrustedCerts](#trustedcerts-property-pdfsign-component), and [TrustedLists](#trustedlists-property-pdfsign-component). |

# ValidationFlags Property ([PDFSign](#pdfsign-component) Component)

Additional chain validation settings.

## Syntax

```text
public int ValidationFlags { get; set; }
```

## Default Value

0

## Remarks

This property is used to specify additional settings that affect the overall flow of the chain validation.

Its value should be provided as a bitmask of the following flags:

|  |  |
| --- | --- |
| 0x001 (cvfForceCompleteChainValidationForTrusted) | Perform full chain validation for explicitly trusted intermediary or end-entity certificates. This may be useful when creating signatures to enforce the completeness of the collected revocation information. It often makes sense to omit this flag when validating signatures to reduce validation time and avoid issues with poorly configured environments. |
| 0x002 (cvfIgnoreChainLoops) | Currently unsupported. |
| 0x004 (cvfIgnoreOCSPNoCheckExtension) | Currently unsupported. |
| 0x008 (cvfTolerateMinorChainIssues) | Currently unsupported. |

# ValidationPolicy Property ([PDFSign](#pdfsign-component) Component)

The level at which to perform chain validation.

## Syntax

```text
public PDFSignValidationPolicies ValidationPolicy { get; set; }
enum PDFSignValidationPolicies {
  vpNone,
  vpFull,
  vpFullNoTrust,
  vpFullNoRevocation,
  vpBestEffort
}
```

## Default Value

1

## Remarks

This property is used to specify the overall validation policy the component follows.

Possible values are:

|  |  |
| --- | --- |
| 0 (vpNone) | No chain validation is attempted at all. |
| 1 (vpFull - default) | Revocation and trust checks must succeed for all chains. |
| 2 (vpFullNoTrust) | Revocation checks must succeed, but trust checks will not occur. |
| 3 (vpFullNoRevocation) | Trust checks must succeed, but revocation checks will not occur. |
| 4 (vpBestEffort) | Currently unsupported. |

### Validation Policy Heuristics

 The choice of validation policy depends on the scenario for which the chain is validated.

**Creating a new signature:**

- For a basic signature with or without a timestamp, chain validation is not required, so it is recommended to use *vpNone*. This policy may also be used in test environments or on offline systems.
- For an LTV signature, use *vpFull* or *vpFullNoTrust* depending on whether trust checks are necessary in the current environment. If the signature is being created in an environment that does not match the prospective validation environment, consider *vpFullNoTrust* to validate the chain properly and fully without expecting good trust.

**Updating or extending an existing signature:**

- When updating a basic signature to LTV, similarly use *vpFull* or *vpFullNoTrust* as above.
- When extending an LTV signature, similarly use *vpFull* or *vpFullNoTrust* as above.

**Validating an existing signature:**

- For basic signature validation, use *vpFullNoRevocation* if trust checks, but not revocation checks, are necessary in the current environment. This policy may also be used on offline systems if the trust anchor is already available to the component.
- For archival validation, use *vpFull* to validate the chain properly and fully. This policy expects the trust anchor and all the revocation material to be available.

# ValidationTime Property ([PDFSign](#pdfsign-component) Component)

The time point at which the signature should be validated.

## Syntax

```text
public string ValidationTime { get; set; }
```

## Default Value

""

## Remarks

This property is used to specify the moment in time at which the signature validity should be established. The time should be provided in UTC in *yyyyMMddHHmmssZ* format.

Leave this property empty to stick to the default time point. The component then prioritizes:

- The signature creation time if the signature contains a signature timestamp ([ValidatedSigningTime](#PDFSignature_f_ValidatedSigningTime)), or
- The local time included in the signature by the signer ([ClaimedSigningTime](#PDFSignature_f_ClaimedSigningTime)).

 NOTE: The validity of the same signature may differ depending on the time point chosen due to temporal changes in chain validities, revocation statuses, and timestamp times.

# AddAttachment Method ([PDFSign](#pdfsign-component) Component)

Adds an attachment to the document.

## Syntax

```text
public void AddAttachment(string fileName, string description);

Async Version
public async Task AddAttachment(string fileName, string description);
public async Task AddAttachment(string fileName, string description, CancellationToken cancellationToken);
```

## Remarks

This method is used to add an attachment (embedded file) to the document and to the [Attachments](#attachments-property-pdfsign-component) collection.

*FileName* and *Description* specify the filename and description of the attachment respectively.

**Example:**

```csharp
component.InputFile = "input.pdf";
component.OutputFile = "input_with_attachment.pdf";
component.Open();
component.AddAttachment("foo.txt", "desc");

// Alternatively, create a PDFAttachment object and add it to Attachments manually:
PDFAttachment attachment = new PDFAttachment();
attachment.FileName = "foo.txt";
// or attachment.DataB = new byte[] { ... };
// or attachment.InputStream = new FileStream(...);
attachment.Description = "desc";
component.Attachments.Add(attachment);

// Or using one of the constructors:
component.Attachments.Add(new PDFAttachment("foo.txt", "desc"));
component.Close();
```

 The full list of attachments is contained in the [Attachments](#attachments-property-pdfsign-component) collection.

NOTE: If the document is not already opened, this method opens it, performs the operation, then closes it.

# AddTimestamp Method ([PDFSign](#pdfsign-component) Component)

Adds a document timestamp to the document.

## Syntax

```text
public void AddTimestamp();

Async Version
public async Task AddTimestamp();
public async Task AddTimestamp(CancellationToken cancellationToken);
```

## Remarks

This method is used to obtain a document timestamp and embed it into the document.

A document timestamp is a fully independent signature that is added to the PDF document after the initial signature. Unlike the main signature, the document timestamp is made by a TSA, and its purpose is to preserve the document's long-term validity. Typically, adding a document timestamp is done close to the expiration date of the certificate that produced the last timestamp (which is either embedded in the main signature, or is a previous document timestamp). An LTV document therefore contains a chain of document timestamps updated periodically to keep its long-term status.

**Example:**

```csharp
pdfsign.InputFile = "signed.pdf";
pdfsign.OutputFile = "signed_with_dts.pdf";
pdfsign.TimestampServer = "http://time.certum.pl";
pdfsign.AddTimestamp();
```

 NOTE: If the document is not already opened, this method opens it, performs the operation, then closes it.

# Close Method ([PDFSign](#pdfsign-component) Component)

Closes the opened document.

## Syntax

```text
public void Close();

Async Version
public async Task Close();
public async Task Close(CancellationToken cancellationToken);
```

## Remarks

This method is used to close the previously opened document. It should always be preceded by a call to [Open](#open-method-pdfsign-component).

**Example:**

```csharp
component.InputFile = "input.pdf";
component.Open();
// Some operation
component.Close();
```

 If any changes are made to the document, they are saved automatically to [OutputFile](#outputfile-property-pdfsign-component), [OutputData](#outputdata-property-pdfsign-component), or the stream set in [SetOutputStream](#setoutputstream-method-pdfsign-component) when this method is called. To configure this saving behavior, set [SaveChanges](#SaveChanges).

# Config Method ([PDFSign](#pdfsign-component) Component)

Sets or retrieves a configuration setting.

## Syntax

```text
public string Config(string configurationString);

Async Version
public async Task<string> Config(string configurationString);
public async Task<string> Config(string configurationString, CancellationToken cancellationToken);
```

## Remarks

Config is a generic method available in every component. It is used to set and retrieve [configuration settings](#config-settings-pdfsign-component) for the component.

These settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these *internal properties* is provided through the Config method.

To set a configuration setting named *PROPERTY*, you must call *Config("PROPERTY=VALUE")*, where *VALUE* is the value of the setting expressed as a string. For boolean values, use the strings "True", "False", "0", "1", "Yes", or "No" (case does not matter).

To read (query) the value of a [configuration setting](#config-settings-pdfsign-component), you must call *Config("PROPERTY")*. The value will be returned as a string.

# Encrypted Method ([PDFSign](#pdfsign-component) Component)

Checks whether the document is encrypted.

## Syntax

```text
public bool Encrypted();

Async Version
public async Task<bool> Encrypted();
public async Task<bool> Encrypted(CancellationToken cancellationToken);
```

## Remarks

This method is used to determine whether the document is encrypted. It returns *false* if the document is pseudo-encrypted with an empty password.

**Example:**

```csharp
component.InputFile = "input.pdf";
if (component.Encrypted())
{
  // Set Password or DecryptionCert
}
component.Open();
// Some operation
component.Close();
```

 NOTE: If the document is not already opened, this method opens it, performs the operation, then closes it.

# GetPageProperty Method ([PDFSign](#pdfsign-component) Component)

Returns the value of a page property.

## Syntax

```text
public string GetPageProperty(int pageIndex, string pageProperty);

Async Version
public async Task<string> GetPageProperty(int pageIndex, string pageProperty);
public async Task<string> GetPageProperty(int pageIndex, string pageProperty, CancellationToken cancellationToken);
```

## Remarks

This method is used to obtain general information about the pages of the document, such as their dimensions and content positioning details.

*PageIndex* specifies the page to read information about (with a valid range from *0* to *PageCount - 1*), and *PageProperty* specifies the page property to read. Possible values are:

| Page property | Default value | Description |
| --- | --- | --- |
| CropLowerLeftX | 0 | The lower-left X coordinate of the page crop area in points. |
| CropLowerLeftY | 0 | The lower-left Y coordinate of the page crop area in points. |
| CropUpperRightX | 0 | The upper-right X coordinate of the page crop area in points. |
| CropUpperRightY | 0 | The upper-right Y coordinate of the page crop area in points. |
| Height | 0 | The height of the page in points. |
| MediaLowerLeftX | 0 | The lower-left X coordinate of the page media area in points. |
| MediaLowerLeftY | 0 | The lower-left Y coordinate of the page media area in points. |
| MediaUpperRightX | 0 | The upper-right X coordinate of the page media area in points. |
| MediaUpperRightY | 0 | The upper-right Y coordinate of the page media area in points. |
| Rotation | 0 | The rotation angle of the page in degrees clockwise. Supported values: 0, 90, 180, 270. |
| Width | 0 | The width of the page in points. |

**Example:**

```csharp
int pageCount = 0;
component.OnDocumentInfo += (s, e) => { pageCount = e.PageCount; };
component.InputFile = "input.pdf";
component.Open();
for (int i = 0; i < pageCount; i++) component.GetPageProperty(i, "Height");
component.Close();
```

 The page properties can be used to adjust the position of the signature widget based on the page dimensions. For example:

```csharp
int x = int.Parse(pdfsign.GetPageProperty(0, "Width")) - 100;
int y = int.Parse(pdfsign.GetPageProperty(0, "Height")) - 100;
pdfsign.SetWidgetProperty("OffsetX", x.ToString());
pdfsign.SetWidgetProperty("OffsetY", y.ToString());
```

 NOTE: Each page property is only populated once the document has been loaded, which is reported by the [DocumentInfo](#documentinfo-event-pdfsign-component) event.

NOTE: If the document is not already opened, this method opens it, performs the operation, then closes it.

# GetWidgetProperty Method ([PDFSign](#pdfsign-component) Component)

Returns the value of a signature widget property.

## Syntax

```text
public string GetWidgetProperty(int signatureIndex, string widgetProperty);

Async Version
public async Task<string> GetWidgetProperty(int signatureIndex, string widgetProperty);
public async Task<string> GetWidgetProperty(int signatureIndex, string widgetProperty, CancellationToken cancellationToken);
```

## Remarks

This method is used to obtain the value of a signature widget property. Together with [SetWidgetProperty](#setwidgetproperty-method-pdfsign-component), this method provides an extensible way of managing the widget settings that are not available through the primary properties of the component. The list of settings below may be extended in the future.

*SignatureIndex* is the index of the signature of interest in the [Signatures](#signatures-property-pdfsign-component) collection, and *WidgetProperty* specifies the widget property to read. Possible values are:

| Widget property | Default value | Description |
| --- | --- | --- |
| BackgroundHeight | 0 | The size of the stretched background image in the vertical direction. |
| BackgroundWidth | 0 | The size of the stretched background image in the horizontal direction. |
| CompressWidgetData | False | Whether to compress the signature widget data before saving. |
| CustomBackgroundContentStream | "" | A custom background content stream to use when BackgroundStyle is set to Custom. |
| CustomTextCount | 0 | The number of custom text blocks on the signature widget. |
| CustomTextFontResourceName[Index] | "" | The font resource name used for the custom text block. |
| CustomTextFontSizeX[Index] | 0 | The horizontal font size scale used for the custom text. |
| CustomTextFontSizeY[Index] | 0 | The vertical font size scale used for the custom text. |
| CustomTextX[Index] | 0 | The horizontal offset of the custom text block on the widget. |
| CustomTextY[Index] | 0 | The vertical offset of the custom text block on the widget. |
| CustomText[Index] | "" | The text shown on a custom signature widget text block. This indexed property provides access to the text placed on a specific signature widget text block. CustomText[0] specifies the text on the first block, CustomText[1] on the second block, and so on. Use CustomTextCount to get the number of custom text blocks. |
| Height | 70 | The height of the signature widget in points. This property is the same as [WidgetHeight](#PDFSignature_f_WidgetHeight). |
| Invisible | False | Whether the signature widget is invisible on the page. |
| OffsetX | 0 | The signature widget offset from the left-hand page border in points. This property is the same as [WidgetOffsetX](#PDFSignature_f_WidgetOffsetX). |
| OffsetY | 0 | The signature widget offset from the bottom page border in points. This property is the same as [WidgetOffsetY](#PDFSignature_f_WidgetOffsetY). |
| Pages | "" | The pages on which the signature is shown. This property is the same as [WidgetPages](#PDFSignature_f_WidgetPages). |
| Rotation | 0 | The rotation angle of the signature widget in degrees clockwise. Supported values: 0, 90, 180, 270. |
| Width | 70 | The width of the signature widget in points. This property is the same as [WidgetWidth](#PDFSignature_f_WidgetWidth). |

**Example:**

```csharp
pdfsign.InputFile = "signed.pdf";
pdfsign.Open();
bool invisible = bool.Parse(pdfsign.GetWidgetProperty(0, "Invisible"));
pdfsign.Close();
```

 NOTE: Each widget property is only populated after the document has been signed and the signature widget has been generated.

NOTE: If the document is not already opened, this method opens it, performs the operation, then closes it.

# Interrupt Method ([PDFSign](#pdfsign-component) Component)

Interrupts the current action.

## Syntax

```text
public void Interrupt();

Async Version
public async Task Interrupt();
public async Task Interrupt(CancellationToken cancellationToken);
```

## Remarks

This method interrupts the current action. It can be used, for example, within the [ChainCert](#chaincert-event-pdfsign-component) event to abort the chain validation procedure.

If there is no action in progress, this method simply returns, doing nothing.

# Open Method ([PDFSign](#pdfsign-component) Component)

Opens the document for processing.

## Syntax

```text
public void Open();

Async Version
public async Task Open();
public async Task Open(CancellationToken cancellationToken);
```

## Remarks

This method is used to open the document specified in [InputFile](#inputfile-property-pdfsign-component), [InputData](#inputdata-property-pdfsign-component), or [SetInputStream](#setinputstream-method-pdfsign-component) before performing some operation on it, such as signing or updating. When finished, call [Close](#close-method-pdfsign-component) to complete or discard the operation.

It is recommended to use this method (alongside [Close](#close-method-pdfsign-component)) when performing multiple operations on the document at once.

NOTE: This method populates the [Attachments](#attachments-property-pdfsign-component), [DocumentCerts](#documentcerts-property-pdfsign-component), and [Signatures](#signatures-property-pdfsign-component) collections with any corresponding objects found in the document.

### Automatic Decryption Functionality

 If this method is called on an encrypted document, the [Password](#password-event-pdfsign-component) or [RecipientInfo](#recipientinfo-event-pdfsign-component) event fires (depending on the encryption type) as a notification that the document must be decrypted before processing can continue.

Once the correct decryption material is supplied, the component then attempts to decrypt the document automatically within this method. When this occurs, the decrypted content is kept in memory so that the document's encrypted status is preserved when it is saved later. Use [Decrypt](PDFDecrypt.md#PDFDecrypt_m_Decrypt) to save a decrypted copy of the document instead.

# RemoveAttachment Method ([PDFSign](#pdfsign-component) Component)

Removes an attachment from the document.

## Syntax

```text
public void RemoveAttachment(int index);

Async Version
public async Task RemoveAttachment(int index);
public async Task RemoveAttachment(int index, CancellationToken cancellationToken);
```

## Remarks

This method is used to remove an attachment from the document and from the [Attachments](#attachments-property-pdfsign-component) collection.

*Index* is the index of the attachment in the [Attachments](#attachments-property-pdfsign-component) collection to be removed.

**Example:**

```csharp
pdfsign.InputFile = "input_with_attachment.pdf";
pdfsign.OutputFile = "attachment_removed.pdf";
pdfsign.Open();
pdfsign.RemoveAttachment(0);

// Alternatively, remove an attachment from Attachments manually:
PDFAttachment attachment = pdfsign.Attachments[0];
pdfsign.Attachments.Remove(attachment);
pdfsign.Close();
```

 NOTE: If the document is not already opened, this method opens it, performs the operation, then closes it.

# Reset Method ([PDFSign](#pdfsign-component) Component)

Resets the component.

## Syntax

```text
public void Reset();

Async Version
public async Task Reset();
public async Task Reset(CancellationToken cancellationToken);
```

## Remarks

This method is used to reset the component's properties and configuration settings to their default values.

# SaveAttachment Method ([PDFSign](#pdfsign-component) Component)

Saves a PDF attachment to a file.

## Syntax

```text
public void SaveAttachment(int index, string fileName);

Async Version
public async Task SaveAttachment(int index, string fileName);
public async Task SaveAttachment(int index, string fileName, CancellationToken cancellationToken);
```

## Remarks

This method is used to retrieve the contents of an attachment from the document and save it to a file. It does not modify the contents of the [Attachments](#attachments-property-pdfsign-component) collection.

*Index* is the index of the attachment in the [Attachments](#attachments-property-pdfsign-component) collection to be saved.

*FileName* specifies the filename that the attachment will be saved to.

**Example:**

```csharp
component.InputFile = "input_with_attachment.pdf";
component.Open();
component.SaveAttachment(0, "a.dat");
component.Close();
```

 **Example (saving to a stream):**

```csharp
component.InputFile = "input_with_attachment.pdf";
component.Attachments[0].OutputStream = myStream;
component.SaveAttachment(0, null); // null means use the OutputStream field if it's set
```

 NOTE: If the document is not already opened, this method opens it, performs the operation, then closes it.

# SetInputStream Method ([PDFSign](#pdfsign-component) Component)

Sets the stream containing the PDF document to process.

## Syntax

```text
public void SetInputStream(System.IO.Stream inputStream);

Async Version
public async Task SetInputStream(System.IO.Stream inputStream);
public async Task SetInputStream(System.IO.Stream inputStream, CancellationToken cancellationToken);
```

## Remarks

This method is used to set the stream from which the component reads the PDF document to be processed. If an input stream is set before the component attempts to perform operations on the document, the component reads the data from the input stream instead of from the [InputFile](#inputfile-property-pdfsign-component) or [InputData](#inputdata-property-pdfsign-component) properties.

NOTE: It may be useful to additionally set [CloseInputStreamAfterProcessing](#CloseInputStreamAfterProcessing) to *true* when using input streams.

# SetOutputStream Method ([PDFSign](#pdfsign-component) Component)

Sets the stream to write the processed document to.

## Syntax

```text
public void SetOutputStream(System.IO.Stream outputStream);

Async Version
public async Task SetOutputStream(System.IO.Stream outputStream);
public async Task SetOutputStream(System.IO.Stream outputStream, CancellationToken cancellationToken);
```

## Remarks

This method is used to set the stream to which the component writes the resulting PDF document. If an output stream is set before the component attempts to perform operations on the document, the component writes the data to the output stream instead of writing to [OutputFile](#outputfile-property-pdfsign-component) or populating [OutputData](#outputdata-property-pdfsign-component).

NOTE: It may be useful to additionally set [CloseOutputStreamAfterProcessing](#CloseOutputStreamAfterProcessing) to *true* when using output streams.

# SetWidgetProperty Method ([PDFSign](#pdfsign-component) Component)

Sets the value of a signature widget property.

## Syntax

```text
public void SetWidgetProperty(string widgetProperty, string value);

Async Version
public async Task SetWidgetProperty(string widgetProperty, string value);
public async Task SetWidgetProperty(string widgetProperty, string value, CancellationToken cancellationToken);
```

## Remarks

This method is used to adjust the look of the signature widget when creating a signature. Together with [GetWidgetProperty](#getwidgetproperty-method-pdfsign-component), this method provides an extensible way of managing the widget settings that are not available through the primary properties of the component. The list of settings below may be extended in the future.

*WidgetProperty* and *Value* specify the widget property and value to set respectively. Possible values for the former are:

| Widget property | Default value | Description |
| --- | --- | --- |
| AlgorithmCaption | #auto | The caption of the signature widget field with information about the signature algorithm. |
| AlgorithmInfo | #auto | Information about the algorithm to be displayed on the signature widget. Keep this property set to #auto to make the component generate the algorithm text automatically, in the form of Algorithm/Key size, for example RSA/1024 bits. |
| AutoReshapeArabicSymbols | True | Whether to automatically reshape Arabic symbols in the signature widget. If disabled, Arabic symbols are written in isolated form. |
| AutoReverseRTLText | True | Whether to automatically detect and reverse right-to-left text to ensure proper visual presentation in the signature widget. |
| BackgroundData | "" | The data of the signature widget background bitmap. Assign the widget background data (in the form of a filename or hex-encoded JPEG or JPEG 2000 bytes) to this property. |
| BackgroundHeight | 0 | The size of the stretched background image in the vertical direction. |
| BackgroundImageColorSpace | "" | The background image color space. Supported values: none, RGB, CMYK, Gray. |
| BackgroundImageHeight | 0 | The height of the background image in pixels. It is important that this property matches the exact size of the image when a custom background is used. The width and height of the background image have no direct relation to the dimensions of the signature widget on the document page, and are only used to indicate the parameters of the image to the PDF processor. Big images are ultimately squeezed to fit into the widget, and smaller ones stretched. |
| BackgroundImageType | JPEG2000 | The type of the image contained in BackgroundData. Supported values: JPEG2000, JPEG, Custom. |
| BackgroundImageWidth | 0 | The width of the background image in pixels. It is important that this property matches the exact size of the image when a custom background is used. The width and height of the background image have no direct relation to the dimensions of the signature widget on the document page, and are only used to indicate the parameters of the image to the PDF processor. Big images are ultimately squeezed to fit into the widget, and smaller ones stretched. |
| BackgroundMask | "" | The hex-encoded bytes of the background image mask. Masks provide a means for marking transparent areas on the signature widget. Specifically, a transparency mask tells PDF viewing applications which pixels of the signature widget should be kept visible and which should be rendered transparent instead. A mask is effectively a matrix of bits, with each bit corresponding to a pixel on the background bitmap. A bit is set to 1 if the corresponding pixel needs to be made transparent, or to 0 if it needs to be opaque. In most cases, a unique mask tailored to the signature widget image is required. This mask should be created based on the actual image design and desired appearance. |
| BackgroundPosition | "" | The position of the widget background image. The value may be the keyword value center, which centers the image, or a pair of coordinates (e.g., 10 5.5) in which the first value defines X and the second defines Y starting from the bottom-left corner. |
| BackgroundStyle | Default | The style of the signature widget background. Supported values: Default, None, Custom. |
| BackgroundWidth | 0 | The size of the stretched background image in the horizontal direction. |
| CompressWidgetData | False | Whether to compress the signature widget data before saving. |
| CustomBackgroundContentStream | "" | A custom background content stream to use when BackgroundStyle is set to Custom. |
| CustomTextCount | 0 | The number of custom text blocks on the signature widget. |
| CustomTextFontResourceName[Index] | "" | The font resource name to use for the custom text block. |
| CustomTextFontSizeX[Index] | 0 | The horizontal font size scale to use for the custom text. |
| CustomTextFontSizeY[Index] | 0 | The vertical font size scale to use for the custom text. |
| CustomTextX[Index] | 0 | The horizontal offset of the custom text block on the widget. |
| CustomTextY[Index] | 0 | The vertical offset of the custom text block on the widget. |
| CustomText[Index] | "" | The text to show on a custom signature widget text block. This indexed property provides access to the text to be placed on a specific signature widget text block. CustomText[0] specifies the text on the first block, CustomText[1] on the second block, and so on. Use CustomTextCount to set the number of custom text blocks. |
| DateFontSize | 0 | The font size of the date and time text on the signature widget. |
| DateFormat | "" | The format string used to display the signing date and time in the signature widget. Leave this property empty (default value) to use the default format. To convert UTC time to local time, set this property to L (default format) or use the L: prefix with a custom date time format string. |
| FontName | "" | The font name for the signature widget text. Use this property to specify a Type 1 or TrueType font name for the signature widget text. If this property is empty, the widget uses the standard PDF Helvetica font. The PDF format supports 14 standard Type 1 fonts: Times-Roman, Helvetica, Courier, Symbol, Times-Bold, Helvetica-Bold, Courier-Bold, ZapfDingbats, Times-Italic, Helvetica-Oblique, Courier-Oblique, Times-BoldItalic, Helvetica-BoldOblique, Courier-BoldOblique. Standard Type 1 fonts are used as standard PDF fonts and are not embedded by the component. Note that Adobe no longer supports Type 1 fonts as of January 2023. If the target document profile, such as PDF/A, requires fonts used in visible text to be embedded, specify a TrueType font. For TrueType fonts, the component supports full font names (e.g., Times New Roman, Arial Bold Italic), filenames (e.g., times.ttf, arialbi.ttf), or full file paths. If a TrueType font is used, then a font subset is embedded into the PDF document. The list of system TrueType font names that are supported by the component can be obtained from the [SystemFontNames](#SystemFontNames) configuration setting. Use the [FontPaths](#FontPaths) configuration setting to specify font search paths when a TrueType font is specified without a full file path. Alternatively, set this property to the full path to the TrueType font file. |
| Header | #auto | The header text to put on the signature widget. Keep this property set to #auto to make the component generate the header automatically. |
| Height | 70 | The height of the signature widget in points. This property is the same as [SignatureWidgetHeight](#signaturewidgetheight-property-pdfsign-component). |
| HideDefaultText | False | Whether to generate default headers for the signature widget. |
| IgnoreExistingAppearance | False | Whether to discard all existing widget parameters when signing empty signature fields. This property only makes sense for signatures created by signing existing empty signature fields with pre-defined widget descriptions. |
| InvertMask | False | Whether to invert the mask set in BackgroundMask by making opaque all the bits declared as transparent, and making transparent all the bits declared as opaque. |
| Invisible | False | Whether the signature widget is invisible on the page. |
| OffsetX | 0 | The signature widget offset from the left-hand page border in points. This property is the same as [SignatureWidgetOffsetX](#signaturewidgetoffsetx-property-pdfsign-component). |
| OffsetY | 0 | The signature widget offset from the bottom page border in points. This property is the same as [SignatureWidgetOffsetY](#signaturewidgetoffsety-property-pdfsign-component). |
| Pages | "" | The pages on which the signature is shown. This property is the same as [SignatureWidgetPages](#signaturewidgetpages-property-pdfsign-component). |
| PositionAnchor | Default | The anchor to bind the position of the widget to. Supported values: Default, BottomLeft, BottomRight, TopLeft, TopRight, Center. |
| RenderOptions | Print | A comma-separated list of rendering options. Supported values: Unknown, NoRotate, NoView, NoZoom, Print, ReadOnly, ToggleNoView. |
| Rotation | 0 | The rotation angle of the signature widget in degrees clockwise. Supported values: 0, 90, 180, 270. |
| SectionTextFontSize | 0 | The font size of general text on the signature widget. |
| SectionTitleFontSize | 0 | The font size of the section title on the signature widget. |
| ShowDate | True | Whether to display the signing date and time details on the widget. |
| SignerCaption | #auto | The caption for the signer section on the signature widget. Keep this property set to #auto to make the component generate the default signer caption, which is Signer: . |
| SignerInfo | #auto | Custom signer information to put on the signature widget. The standard signature widget allows for several short strings separated by carriage return line feed (CRLF). Keep this property set to #auto to make the component generate the signer text automatically. |
| TitleFontSize | 0 | The font size of the main title on the signature widget. |
| UseArabicLigature | False | Whether to enable Arabic ligatures in the signature widget. If enabled, certain adjacent Arabic characters may be combined and rendered as a single ligature form (if supported by the shaping engine or font), improving the natural appearance of the text. If disabled, characters are rendered without ligature substitution, and only basic contextual shaping is applied (if AutoReshapeArabicSymbols is enabled). |
| Width | 70 | The width of the signature widget in points. This property is the same as [SignatureWidgetWidth](#signaturewidgetwidth-property-pdfsign-component). |

**Example:**

```csharp
pdfsign.SetWidgetProperty("Width", "100");
pdfsign.SetWidgetProperty("Height", "100");
pdfsign.SetWidgetProperty("ShowDate", "false");
pdfsign.SetWidgetProperty("SignerInfo", "Hello\r\nworld!");
pdfsign.SetWidgetProperty("TitleFontSize", "11");
pdfsign.Sign();
```

# Sign Method ([PDFSign](#pdfsign-component) Component)

Signs the data.

## Syntax

```text
public void Sign();

Async Version
public async Task Sign();
public async Task Sign(CancellationToken cancellationToken);
```

## Remarks

This method is used to sign the document or its hash. If [RemoteSignatureMethod](#remotesignaturemethod-property-pdfsign-component) is set to *rsmNone* or *rsmDigest*, the input data is signed directly with [SigningCert](#signingcert-property-pdfsign-component). Otherwise, if it is set to *rsmPKCS1* or *rsmPKCS7*, the document is "pre-signed" with the configured signature settings and [RemoteSignatureDigest](#remotesignaturedigest-property-pdfsign-component) is populated with the data to be signed remotely.

Use the following properties to adjust new signature settings:

- [SignatureAuthorName](#signatureauthorname-property-pdfsign-component)
- [SignatureClaimedSigningTime](#signatureclaimedsigningtime-property-pdfsign-component)
- [SignatureHashAlgorithm](#signaturehashalgorithm-property-pdfsign-component)
- [SignatureProfile](#signatureprofile-property-pdfsign-component)
- [SignatureReason](#signaturereason-property-pdfsign-component)
- [SignatureType](#signaturetype-property-pdfsign-component)
- [SignatureWidgetHeight](#signaturewidgetheight-property-pdfsign-component)
- [SignatureWidgetOffsetX](#signaturewidgetoffsetx-property-pdfsign-component)
- [SignatureWidgetOffsetY](#signaturewidgetoffsety-property-pdfsign-component)
- [SignatureWidgetPages](#signaturewidgetpages-property-pdfsign-component)
- [SignatureWidgetWidth](#signaturewidgetwidth-property-pdfsign-component)

Use the following properties to adjust chain validation parameters:

- [BlockedCerts](#blockedcerts-property-pdfsign-component)
- [KnownCerts](#knowncerts-property-pdfsign-component)
- [OfflineMode](#offlinemode-property-pdfsign-component)
- [RevocationCheck](#revocationcheck-property-pdfsign-component)
- [TrustedCerts](#trustedcerts-property-pdfsign-component)
- [TrustedLists](#trustedlists-property-pdfsign-component)
- [TrustSources](#trustsources-property-pdfsign-component)
- [ValidationFlags](#validationflags-property-pdfsign-component)
- [ValidationPolicy](#validationpolicy-property-pdfsign-component)
- [ValidationTime](#validationtime-property-pdfsign-component)

 During signing, the chain validation log is available via the [Log](#log-event-pdfsign-component) event if applicable.

NOTE: If the document is not already opened, this method opens it, performs the operation, then closes it.

# Signed Method ([PDFSign](#pdfsign-component) Component)

Checks whether the document is signed.

## Syntax

```text
public bool Signed();

Async Version
public async Task<bool> Signed();
public async Task<bool> Signed(CancellationToken cancellationToken);
```

## Remarks

This method is used to determine whether the document is signed. It returns *false* if the document contains only empty signature fields.

**Example:**

```csharp
pdfsign.InputFile = "input.pdf";
if (!pdfsign.Signed())
{
  pdfsign.OutputFile = "signed.pdf";
  pdfsign.SigningCert = new Certificate(CertStoreTypes.cstPFXFile, "cert.pfx", "password", "*");
  // Configure signature-related properties as desired
  pdfsign.Sign();
}
```

 NOTE: If the document is not already opened, this method opens it, performs the operation, then closes it.

# Update Method ([PDFSign](#pdfsign-component) Component)

Updates the most recent signature.

## Syntax

```text
public void Update();

Async Version
public async Task Update();
public async Task Update(CancellationToken cancellationToken);
```

## Remarks

This method is used to update the most recent signature by embedding newer or missing revocation information into the signed document.

Updating a signature starts with its cryptographic validation. Before any new validation material is inserted, the signature's integrity must be validated. If the signature is found to be correct, the component proceeds with chain validation and the retrieval of any missing chain elements. If the signature is cryptographically wrong, the component throws an exception.

The update approach is typically used to extend the validity of an LTV signature. For LTA signatures, updating is typically accompanied with a document timestamping operation. Set [TimestampServer](#timestampserver-property-pdfsign-component) to have the component obtain and embed a document timestamp automatically.

Further validation material and document timestamps may be added to a document over time to maintain its authenticity and integrity.

Use the following properties to adjust chain validation parameters:

- [BlockedCerts](#blockedcerts-property-pdfsign-component)
- [KnownCerts](#knowncerts-property-pdfsign-component)
- [OfflineMode](#offlinemode-property-pdfsign-component)
- [RevocationCheck](#revocationcheck-property-pdfsign-component)
- [TrustedCerts](#trustedcerts-property-pdfsign-component)
- [TrustedLists](#trustedlists-property-pdfsign-component)
- [TrustSources](#trustsources-property-pdfsign-component)
- [ValidationFlags](#validationflags-property-pdfsign-component)
- [ValidationPolicy](#validationpolicy-property-pdfsign-component)
- [ValidationTime](#validationtime-property-pdfsign-component)

NOTE: To choose a different signature to update, set [UpdateIndex](#UpdateIndex).

NOTE: If the document is not already opened, this method opens it, performs the operation, then closes it.

# ChainCert Event ([PDFSign](#pdfsign-component) Component)

Fired when the component encounters a chain certificate.

## Syntax

```text
public event OnChainCertHandler OnChainCert;

public delegate void OnChainCertHandler(object sender, PDFSignChainCertEventArgs e);

public class PDFSignChainCertEventArgs : EventArgs {
  public string CertEncoded { get; }  public byte[] CertEncodedB { get; }
  public string CertSubject { get; }
  public string CertIssuer { get; }
  public string ValidationTime { get; }
  public int ValidationResult { get; set; }
  public int ValidationDetails { get; set; }
}
```

## Remarks

This event is fired once for each certificate encountered during chain validation to report that it is about to be processed. The component tries to retrieve all required chain certificates automatically.

*CertEncoded* specifies the PEM (Base64-encoded) public certificate.

*CertSubject* and *CertIssuer* specify the distinguished names of the certificate owner and issuer respectively.

*ValidationTime* specifies the time point (in UTC) at which the certificate validity was established.

*ValidationResult* reports the outcome of the individual certificate validation and can be one of the following values:

|  |  |
| --- | --- |
| 0 (cvrUnknown - default) | Certificate validity is unknown. |
| 1 (cvrValid) | The certificate is valid. |
| 2 (cvrValidButUntrusted) | The certificate is valid but not trusted. |
| 3 (cvrInvalid) | The certificate is not valid (it is revoked, expired, or contains an invalid signature). |
| 4 (cvrCantBeEstablished) | The validity of the certificate cannot be established because of missing or unavailable validation information (certificates, CRLs, or OCSP responses). |

In the case of a failure, *ValidationDetails* provides more details on its reasons. Its value is a bitmask of the following flags:

|  |  |
| --- | --- |
| 0x001 (cvdRevoked) | The certificate is revoked. |
| 0x002 (cvdExpiredOrNotYetValid) | The certificate is expired or not yet valid. |
| 0x004 (cvdUnknownCA) | A CA certificate for the certificate has not been found, is not trusted, or has a wrong public key (chain incomplete). |
| 0x008 (cvdPolicyViolated) | One of the CA certificates is not authorized to act as a CA, a mandatory key usage is not enabled, or a weak algorithm is used in the certificate. |
| 0x010 (cvdRevocationCheckFailed) | One or more CRLs or OCSP responses could not be verified. |
| 0x020 (cvdBlocked) | The certificate is blocked. |
| 0x040 (cvdFailure) | General validation failure. |

### Overridable Chain Validation

 While the component follows the validation rules defined by the X.509 standard to the best of its ability, minor technical issues may arise when validating the chain. The *ValidationResult* and *ValidationDetails* parameters can be overridden to relax such requirements on a per-certificate basis.

For example, set *ValidationResult* to *cvrValid* and *ValidationDetails* to *0* in order to:

- Ignore CA or TLS key usage requirements
- Ignore the AuthorityKeyId extension in certificate-issuing CAs (helps with incorrectly renewed certificates)
- Ignore the Basic Constraints or Name Constraints extensions of CA certificates
- Tolerate some weaker algorithms
- Implicitly trust self-signed certificates
- Skip validity period checks for trusted certificates (helps with older devices that have expired root certificates)
- Ignore chain loops (helps with buggy CAs that include subchains that sign themselves)

 Based on the adjusted validity of the certificate that is currently being processed, the component continues or aborts the chain validation procedure accordingly as if it had arrived at the chosen validation result itself.

NOTE: The user code is ultimately responsible for certificate validity decisions made via these two parameters. If their values are modified within this event, the resulting chain validation procedure may deviate from the standard.

# DocumentInfo Event ([PDFSign](#pdfsign-component) Component)

Fired when the document has been loaded into memory.

## Syntax

```text
public event OnDocumentInfoHandler OnDocumentInfo;

public delegate void OnDocumentInfoHandler(object sender, PDFSignDocumentInfoEventArgs e);

public class PDFSignDocumentInfoEventArgs : EventArgs {
  public int PageCount { get; }
  public int SignatureCount { get; }
}
```

## Remarks

This event is fired once per document processing routine to report that the document has been processed and loaded into memory.

The handler for this event is a good place to check the document structure and access document-related information such as page number and document file details. These may be useful when preparing the signature. For example, [GetPageProperty](#getpageproperty-method-pdfsign-component) can be used to find the optimal position for the signature widget.

*PageCount* reports the number of pages in the document.

*SignatureCount* reports the number of signatures in the document.

This event is fired when [Open](#open-method-pdfsign-component) is called, but only after [Password](#password-event-pdfsign-component) or [RecipientInfo](#recipientinfo-event-pdfsign-component) is fired (if applicable) and the document has been decrypted.

# Error Event ([PDFSign](#pdfsign-component) Component)

Fired when information is available about errors during data delivery.

## Syntax

```text
public event OnErrorHandler OnError;

public delegate void OnErrorHandler(object sender, PDFSignErrorEventArgs e);

public class PDFSignErrorEventArgs : EventArgs {
  public int ErrorCode { get; }
  public string Description { get; }
}
```

## Remarks

The Error event is fired in case of exceptional conditions during message processing. Normally the component throws an exception.

The *ErrorCode* parameter contains an error code, and the *Description* parameter contains a textual description of the error. For a list of valid error codes and their descriptions, please refer to the [Error Codes](#trappable-errors-pdfsign-component) section.

# Log Event ([PDFSign](#pdfsign-component) Component)

Fired once for each log message.

## Syntax

```text
public event OnLogHandler OnLog;

public delegate void OnLogHandler(object sender, PDFSignLogEventArgs e);

public class PDFSignLogEventArgs : EventArgs {
  public int LogLevel { get; }
  public string Message { get; }
  public string LogType { get; }
}
```

## Remarks

This event is fired once for each log message generated by the component. The verbosity is controlled by the [LogLevel](#LogLevel) configuration setting.

*LogLevel* indicates the detail level of the message. Possible values are:

|  |  |
| --- | --- |
| 0 (None) | No messages are logged. |
| 1 (Info - default) | Informational events such as the basics of the chain validation procedure are logged. |
| 2 (Verbose) | Detailed data such as HTTP requests are logged. |
| 3 (Debug) | Debug data including the full chain validation procedure are logged. |

*Message* is the log message.

*LogType* identifies the type of log entry. Possible values are:

- CertValidator
- Font
- HTTP
- PDFInvalidSignature
- PDFRevocationInfo
- Timestamp
- TSL

# Password Event ([PDFSign](#pdfsign-component) Component)

Fired when the component detects that the document is encrypted with a password.

## Syntax

```text
public event OnPasswordHandler OnPassword;

public delegate void OnPasswordHandler(object sender, PDFSignPasswordEventArgs e);

public class PDFSignPasswordEventArgs : EventArgs {
  public bool Available { get; }
  public bool Cancel { get; set; }
}
```

## Remarks

This event is fired during document processing to report that the document is encrypted with a password. It may be used to supply the correct decryption password to [Password](#password-property-pdfsign-component).

*Available* indicates whether the decryption password is already available to the component or still needs to be set. If this parameter is *false*, the correct password must be provided for the decryption attempt to succeed.

*Cancel* determines whether the component will stop firing this event to request a password.

# RecipientInfo Event ([PDFSign](#pdfsign-component) Component)

Fired for each recipient certificate of the encrypted document.

## Syntax

```text
public event OnRecipientInfoHandler OnRecipientInfo;

public delegate void OnRecipientInfoHandler(object sender, PDFSignRecipientInfoEventArgs e);

public class PDFSignRecipientInfoEventArgs : EventArgs {
  public string Issuer { get; }
  public string SerialNumber { get; }
  public string SubjectKeyIdentifier { get; }
  public bool Available { get; }
  public bool Cancel { get; set; }
}
```

## Remarks

This event is fired during document processing for each recipient certificate that the document has been encrypted for (if applicable). It may be used to identify the certificate(s) to load and supply to [DecryptionCert](#decryptioncert-property-pdfsign-component).

*Issuer* specifies the subject of the issuer certificate.

*SerialNumber* specifies the serial number of the encryption certificate.

*SubjectKeyIdentifier* specifies the X.509 subjectKeyIdentifier extension value of the encryption certificate, encoded as a hex string.

*Available* indicates whether the decryption certificate is already available to the component or still needs to be set. If this parameter is *false*, the correct certificate must be provided for the decryption attempt to succeed.

*Cancel* determines whether the component will stop firing this event to request a certificate.

NOTE: The document may be encrypted with more than one certificate (or have "more than one recipient"), in which case each certificate causes its own invocation of this event.

# SignatureInfo Event ([PDFSign](#pdfsign-component) Component)

Fired when the component finds a signature in the document.

## Syntax

```text
public event OnSignatureInfoHandler OnSignatureInfo;

public delegate void OnSignatureInfoHandler(object sender, PDFSignSignatureInfoEventArgs e);

public class PDFSignSignatureInfoEventArgs : EventArgs {
  public int SignatureIndex { get; }
  public bool ValidateSignature { get; set; }
  public bool ValidateChain { get; set; }
}
```

## Remarks

This event is fired once for each signature found in the document to report that it is about to be validated.

*SignatureIndex* is the index of the signature in the [Signatures](#signatures-property-pdfsign-component) collection.

Signature validation consists of two independent stages: cryptographic signature validation and chain validation. *ValidateSignature* and *ValidateChain* determine whether each stage should be included in the validation. They can be overridden to modify the validation policy on a per-signature basis, allowing signatures to be verified individually instead of all at once (via [Verify](PDFVerify.md#PDFVerify_m_Verify)). To skip validation entirely, set both parameters to *false*.

Use the following properties to adjust chain validation parameters:

- [BlockedCerts](#blockedcerts-property-pdfsign-component)
- [KnownCerts](#knowncerts-property-pdfsign-component)
- [OfflineMode](#offlinemode-property-pdfsign-component)
- [RevocationCheck](#revocationcheck-property-pdfsign-component)
- [TrustedCerts](#trustedcerts-property-pdfsign-component)
- [TrustedLists](#trustedlists-property-pdfsign-component)
- [TrustSources](#trustsources-property-pdfsign-component)
- [ValidationFlags](#validationflags-property-pdfsign-component)
- [ValidationPolicy](#validationpolicy-property-pdfsign-component)
- [ValidationTime](#validationtime-property-pdfsign-component)

# SignatureProcessed Event ([PDFSign](#pdfsign-component) Component)

Fired after a signature has been processed.

## Syntax

```text
public event OnSignatureProcessedHandler OnSignatureProcessed;

public delegate void OnSignatureProcessedHandler(object sender, PDFSignSignatureProcessedEventArgs e);

public class PDFSignSignatureProcessedEventArgs : EventArgs {
  public int SignatureIndex { get; }
  public int SignatureValidationResult { get; }
  public int ChainValidationResult { get; }
  public int ChainValidationDetails { get; }
}
```

## Remarks

This event is fired once for each signature found in the document to report that it has completed validation. It is fired after [SignatureInfo](#signatureinfo-event-pdfsign-component) if that event's *ValidateSignature* parameter is set to *true*.

*SignatureIndex* is the index of the signature in the [Signatures](#signatures-property-pdfsign-component) collection.

Signature validation consists of two independent stages: cryptographic signature validation and chain validation. Separate validation results are reported for each in *SignatureValidationResult* and *ChainValidationResult*.

The former reports the validity of the signature and can be one of the following values:

|  |  |
| --- | --- |
| 0 (svrUnknown - default) | Signature validity is unknown. |
| 1 (svrValid) | The signature is valid. |
| 2 (svrCorrupted) | The signature is corrupted. |
| 3 (svrSignerNotFound) | Failed to acquire the signing certificate. The signature cannot be validated. |
| 4 (svrFailure) | General failure. |

The latter reports the validity of the chain and can be one of the following values:

|  |  |
| --- | --- |
| 0 (cvrUnknown - default) | Chain validity is unknown. |
| 1 (cvrValid) | The chain is valid. |
| 2 (cvrValidButUntrusted) | The chain is valid, but the root certificate is not trusted. |
| 3 (cvrInvalid) | The chain is not valid (some of the certificates are revoked, expired, or contain an invalid signature). |
| 4 (cvrCantBeEstablished) | The validity of the chain cannot be established because of missing or unavailable validation information (certificates, CRLs, or OCSP responses). |

In the case of a failure, *ChainValidationDetails* provides more details on its reasons. Its value is a bitmask of the following flags:

|  |  |
| --- | --- |
| 0x001 (cvdRevoked) | One or more certificates are revoked. |
| 0x002 (cvdExpiredOrNotYetValid) | One or more certificates are expired or not yet valid. |
| 0x004 (cvdUnknownCA) | A CA certificate for one or more certificates has not been found, is not trusted, or has a wrong public key (chain incomplete). |
| 0x008 (cvdPolicyViolated) | One of the CA certificates is not authorized to act as a CA, a mandatory key usage is not enabled in one of the chain certificates, or a weak algorithm is used in one of the certificates or revocation elements. |
| 0x010 (cvdRevocationCheckFailed) | One or more CRLs or OCSP responses could not be verified. |
| 0x020 (cvdBlocked) | One or more certificates are blocked. |
| 0x040 (cvdFailure) | General validation failure. |

NOTE: *SignatureValidationResult*, *ChainValidationResult*, and *ChainValidationDetails* are also available as fields in the [PDFSignature](#pdfsignature-type) type.

# SSLServerAuthentication Event ([PDFSign](#pdfsign-component) Component)

Fired after the server presents its certificate to the client.

## Syntax

```text
public event OnSSLServerAuthenticationHandler OnSSLServerAuthentication;

public delegate void OnSSLServerAuthenticationHandler(object sender, PDFSignSSLServerAuthenticationEventArgs e);

public class PDFSignSSLServerAuthenticationEventArgs : EventArgs {
  public string CertEncoded { get; }  public byte[] CertEncodedB { get; }
  public string CertSubject { get; }
  public string CertIssuer { get; }
  public string Status { get; }
  public bool Accept { get; set; }
}
```

## Remarks

This event is fired during timestamping or chain validation after the server presents its SSL/TLS certificate to the component. It only applies if the TSA, CRL, OCSP, or Trusted List endpoint operates over HTTPS.

During this event, the client can decide whether to continue with the connection process. *Accept* is a recommendation on whether to continue or close the connection. This is just a suggestion: application software must use its own logic to determine whether to continue.

When *Accept* is *false*, *Status* shows why the verification failed (otherwise, *Status* contains the string *OK*). If it is decided to continue, you can override and accept the certificate by setting *Accept* to *true*.

# SSLStatus Event ([PDFSign](#pdfsign-component) Component)

Fired when secure connection progress messages are available.

## Syntax

```text
public event OnSSLStatusHandler OnSSLStatus;

public delegate void OnSSLStatusHandler(object sender, PDFSignSSLStatusEventArgs e);

public class PDFSignSSLStatusEventArgs : EventArgs {
  public string Message { get; }
}
```

## Remarks

This event is fired during timestamping or chain validation for informational and logging purposes only. This event tracks the progress of the SSL/TLS connection. It only applies if the TSA, CRL, OCSP, or Trusted List endpoint operates over HTTPS.

# Certificate Type

This is the digital certificate being used.

## Remarks

This type describes the current digital certificate. The certificate may be a public or private key. The fields are used to identify or select certificates.

The following fields are available:

- [EffectiveDate](#Certificate_f_EffectiveDate)

- [ExpirationDate](#Certificate_f_ExpirationDate)

- [ExtendedKeyUsage](#Certificate_f_ExtendedKeyUsage)

- [Fingerprint](#Certificate_f_Fingerprint)

- [FingerprintSHA1](#Certificate_f_FingerprintSHA1)

- [FingerprintSHA256](#Certificate_f_FingerprintSHA256)

- [Issuer](#Certificate_f_Issuer)

- [PrivateKey](#Certificate_f_PrivateKey)

- [PrivateKeyAvailable](#Certificate_f_PrivateKeyAvailable)

- [PrivateKeyContainer](#Certificate_f_PrivateKeyContainer)

- [PublicKey](#Certificate_f_PublicKey)

- [PublicKeyAlgorithm](#Certificate_f_PublicKeyAlgorithm)

- [PublicKeyLength](#Certificate_f_PublicKeyLength)

- [SerialNumber](#Certificate_f_SerialNumber)

- [SignatureAlgorithm](#Certificate_f_SignatureAlgorithm)

- [Store](#Certificate_f_Store)

- [StorePassword](#Certificate_f_StorePassword)

- [StoreType](#Certificate_f_StoreType)

- [SubjectAltNames](#Certificate_f_SubjectAltNames)

- [ThumbprintMD5](#Certificate_f_ThumbprintMD5)

- [ThumbprintSHA1](#Certificate_f_ThumbprintSHA1)

- [ThumbprintSHA256](#Certificate_f_ThumbprintSHA256)

- [Usage](#Certificate_f_Usage)

- [UsageFlags](#Certificate_f_UsageFlags)

- [Version](#Certificate_f_Version)

- [Subject](#Certificate_f_Subject)

- [Encoded](#Certificate_f_Encoded)

## Fields

 **EffectiveDate** *string (read-only)*
Default: ""

The date on which this certificate becomes valid. Before this date, it is not valid. The date is localized to the system's time zone. The following example illustrates the format of an encoded date:

23-Jan-2000 15:00:00.

 **ExpirationDate** *string (read-only)*
Default: ""

The date on which the certificate expires. After this date, the certificate will no longer be valid. The date is localized to the system's time zone. The following example illustrates the format of an encoded date:

23-Jan-2001 15:00:00.

 **ExtendedKeyUsage** *string (read-only)*
Default: ""

A comma-delimited list of extended key usage identifiers. These are the same as ASN.1 object identifiers (OIDs).

 **Fingerprint** *string (read-only)*
Default: ""

The hex-encoded, 16-byte MD5 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: *bc:2a:72:af:fe:58:17:43:7a:5f:ba:5a:7c:90:f7:02*

 **FingerprintSHA1** *string (read-only)*
Default: ""

The hex-encoded, 20-byte SHA-1 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: *30:7b:fa:38:65:83:ff:da:b4:4e:07:3f:17:b8:a4:ed:80:be:ff:84*

 **FingerprintSHA256** *string (read-only)*
Default: ""

The hex-encoded, 32-byte SHA-256 fingerprint of the certificate. This property is primarily used for keys which do not have a corresponding X.509 public certificate, such as PEM keys that only contain a private key. It is commonly used for SSH keys.

The following example illustrates the format: *6a:80:5c:33:a9:43:ea:b0:96:12:8a:64:96:30:ef:4a:8a:96:86:ce:f4:c7:be:10:24:8e:2b:60:9e:f3:59:53*

 **Issuer** *string (read-only)*
Default: ""

The issuer of the certificate. This field contains a string representation of the name of the issuing authority for the certificate.

 **PrivateKey** *string (read-only)*
Default: ""

The private key of the certificate (if available). The key is provided as PEM/Base64-encoded data.

NOTE: The [PrivateKey](#Certificate_f_PrivateKey) may be available but not exportable. In this case, [PrivateKey](#Certificate_f_PrivateKey) returns an empty string.

 **PrivateKeyAvailable** *bool (read-only)*
Default: False

Whether a [PrivateKey](#Certificate_f_PrivateKey) is available for the selected certificate. If [PrivateKeyAvailable](#Certificate_f_PrivateKeyAvailable) is True, the certificate may be used for authentication purposes (e.g., server authentication).

 **PrivateKeyContainer** *string (read-only)*
Default: ""

The name of the [PrivateKey](#Certificate_f_PrivateKey) container for the certificate (if available). This functionality is available only on Windows platforms.

 **PublicKey** *string (read-only)*
Default: ""

The public key of the certificate. The key is provided as PEM/Base64-encoded data.

 **PublicKeyAlgorithm** *string (read-only)*
Default: ""

The textual description of the certificate's public key algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_DH") or an object identifier (OID) string representing the algorithm.

 **PublicKeyLength** *int (read-only)*
Default: 0

The length of the certificate's public key (in bits). Common values are 512, 1024, and 2048.

 **SerialNumber** *string (read-only)*
Default: ""

The serial number of the certificate encoded as a string. The number is encoded as a series of hexadecimal digits, with each pair representing a byte of the serial number.

 **SignatureAlgorithm** *string (read-only)*
Default: ""

The text description of the certificate's signature algorithm. The property contains either the name of the algorithm (e.g., "RSA" or "RSA_MD5RSA") or an object identifier (OID) string representing the algorithm.

 **Store** *string*
Default: "MY"

The name of the certificate store for the client certificate.

The [StoreType](#Certificate_f_StoreType) field denotes the type of the certificate store specified by [Store](#Certificate_f_Store). If the store is password-protected, specify the password in [StorePassword](#Certificate_f_StorePassword).

[Store](#Certificate_f_Store) is used in conjunction with the [Subject](#Certificate_f_Subject) field to specify client certificates. If [Store](#Certificate_f_Store) has a value, and [Subject](#Certificate_f_Subject) or [Encoded](#Certificate_f_Encoded) is set, a search for a certificate is initiated. Please see the [Subject](#Certificate_f_Subject) field for details.

 Designations of certificate stores are platform dependent.

The following designations are the most common User and Machine certificate stores in Windows:

|  |  |
| --- | --- |
| MY | A certificate store holding personal certificates with their associated private keys. |
| CA | Certifying authority certificates. |
| ROOT | Root certificates. |

When the certificate store type is *cstPFXFile*, this property must be set to the name of the file. When the type is *cstPFXBlob*, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store).

 **StoreB** *byte []*
Default: "MY"

The name of the certificate store for the client certificate.

The [StoreType](#Certificate_f_StoreType) field denotes the type of the certificate store specified by [Store](#Certificate_f_Store). If the store is password-protected, specify the password in [StorePassword](#Certificate_f_StorePassword).

[Store](#Certificate_f_Store) is used in conjunction with the [Subject](#Certificate_f_Subject) field to specify client certificates. If [Store](#Certificate_f_Store) has a value, and [Subject](#Certificate_f_Subject) or [Encoded](#Certificate_f_Encoded) is set, a search for a certificate is initiated. Please see the [Subject](#Certificate_f_Subject) field for details.

 Designations of certificate stores are platform dependent.

The following designations are the most common User and Machine certificate stores in Windows:

|  |  |
| --- | --- |
| MY | A certificate store holding personal certificates with their associated private keys. |
| CA | Certifying authority certificates. |
| ROOT | Root certificates. |

When the certificate store type is *cstPFXFile*, this property must be set to the name of the file. When the type is *cstPFXBlob*, the property must be set to the binary contents of a PFX file (i.e., PKCS#12 certificate store).

 **StorePassword** *string*
Default: ""

If the type of certificate store requires a password, this field is used to specify the password needed to open the certificate store.

 **StoreType** *CertStoreTypes*
Default: 0

The type of certificate store for this certificate.

 The component supports both public and private keys in a variety of formats. When the *cstAuto* value is used, the component will automatically determine the type. This field can take one of the following values:

```csharp
sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11,
                               @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll",
                               "123456", // PIN
                               "CN=cert_subject");
sftp.SSHUser = "test";
sftp.SSHLogon("myhost", 22);
```

```csharp
certmgr.CertStoreType = CertStoreTypes.cstPKCS11;
certmgr.OnCertList += (s, e) => {
  secKeyBlob = e.CertEncoded;
};
certmgr.CertStore = @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll";
certmgr.CertStorePassword = "123456"; // PIN
certmgr.ListStoreCertificates();

sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11, secKeyBlob, "123456", "*");
sftp.SSHUser = "test";
sftp.SSHLogon("myhost", 22);
```

|  |  |
| --- | --- |
| 0 (cstUser - default) | For Windows, this specifies that the certificate store is a certificate store owned by the current user. NOTE: This store type is not available in Java. |
| 1 (cstMachine) | For Windows, this specifies that the certificate store is a machine store. NOTE: This store type is not available in Java. |
| 2 (cstPFXFile) | The certificate store is the name of a PFX (PKCS#12) file containing certificates. |
| 3 (cstPFXBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in PFX (PKCS#12) format. |
| 4 (cstJKSFile) | The certificate store is the name of a Java Key Store (JKS) file containing certificates. NOTE: This store type is only available in Java. |
| 5 (cstJKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in Java Key Store (JKS) format. NOTE: This store type is only available in Java. |
| 6 (cstPEMKeyFile) | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. |
| 7 (cstPEMKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a private key and an optional certificate. |
| 8 (cstPublicKeyFile) | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. |
| 9 (cstPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a PEM- or DER-encoded public key certificate. |
| 10 (cstSSHPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains an SSH-style public key. |
| 11 (cstP7BFile) | The certificate store is the name of a PKCS#7 file containing certificates. |
| 12 (cstP7BBlob) | The certificate store is a string (binary) representing a certificate store in PKCS#7 format. |
| 13 (cstSSHPublicKeyFile) | The certificate store is the name of a file that contains an SSH-style public key. |
| 14 (cstPPKFile) | The certificate store is the name of a file that contains a PPK (PuTTY Private Key). |
| 15 (cstPPKBlob) | The certificate store is a string (binary) that contains a PPK (PuTTY Private Key). |
| 16 (cstXMLFile) | The certificate store is the name of a file that contains a certificate in XML format. |
| 17 (cstXMLBlob) | The certificate store is a string that contains a certificate in XML format. |
| 18 (cstJWKFile) | The certificate store is the name of a file that contains a JWK (JSON Web Key). |
| 19 (cstJWKBlob) | The certificate store is a string that contains a JWK (JSON Web Key). |
| 21 (cstBCFKSFile) | The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store). NOTE: This store type is only available in Java and .NET. |
| 22 (cstBCFKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format. NOTE: This store type is only available in Java and .NET. |
| 23 (cstPKCS11) | The certificate is present on a physical security key accessible via a PKCS#11 interface. To use a security key, create a new [Certificate](#certificate-type) object and pass cstPKCS11 as the [StoreType](#Certificate_f_StoreType), the full path of the PKCS#11 DLL as the [Store](#Certificate_f_Store), and the PIN as the [StorePassword](#Certificate_f_StorePassword). Code Example. SSH Authentication with Security Key (without CertMgr): Alternatively, collect the necessary data using the [CertMgr](CertMgr.md#CertMgr) component by calling the [ListStoreCertificates](CertMgr.md#CertMgr_m_ListStoreCertificates) method after setting the corresponding properties accordingly. The certificate information returned in the [CertList](CertMgr.md#CertMgr_e_CertList) event's CertEncoded parameter may be saved for later use. When using a certificate obtained with this approach, pass the previously saved security key information as the [Store](#Certificate_f_Store) and set [StorePassword](#Certificate_f_StorePassword) to the PIN. Code Example. SSH Authentication with Security Key (with CertMgr): |
| 99 (cstAuto) | The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically. |

 **SubjectAltNames** *string (read-only)*
Default: ""

Comma-separated lists of alternative subject names for the certificate.

 **ThumbprintMD5** *string (read-only)*
Default: ""

The MD5 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

 **ThumbprintSHA1** *string (read-only)*
Default: ""

The SHA-1 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

 **ThumbprintSHA256** *string (read-only)*
Default: ""

The SHA-256 hash of the certificate. It is primarily used for X.509 certificates. If the hash does not already exist, it is automatically computed.

 **Usage** *string (read-only)*
Default: ""

The text description of [UsageFlags](#Certificate_f_UsageFlags).

This value will be one or more of the following strings and will be separated by commas:

- Digital Signature
- Non-Repudiation
- Key Encipherment
- Data Encipherment
- Key Agreement
- Certificate Signing
- CRL Signing
- Encipher Only

If the provider is OpenSSL, the value is a comma-separated list of X.509 certificate extension names.

 **UsageFlags** *int (read-only)*
Default: 0

The flags that show intended use for the certificate. The value of [UsageFlags](#Certificate_f_UsageFlags) is a combination of the following flags:

|  |  |
| --- | --- |
| 0x80 | Digital Signature |
| 0x40 | Non-Repudiation |
| 0x20 | Key Encipherment |
| 0x10 | Data Encipherment |
| 0x08 | Key Agreement |
| 0x04 | Certificate Signing |
| 0x02 | CRL Signing |
| 0x01 | Encipher Only |

Please see the [Usage](#Certificate_f_Usage) field for a text representation of [UsageFlags](#Certificate_f_UsageFlags).

This functionality currently is not available when the provider is OpenSSL.

 **Version** *string (read-only)*
Default: ""

The certificate's version number. The possible values are the strings "V1", "V2", and "V3".

 **Subject** *string*
Default: ""

The subject of the certificate used for client authentication.

This field will be populated with the full subject of the loaded certificate. When loading a certificate, the subject is used to locate the certificate in the store.

If an exact match is not found, the store is searched for subjects containing the value of the property.

If a match is still not found, the property is set to an empty string, and no certificate is selected.

The special value "*" picks a random certificate in the certificate store.

The certificate subject is a comma-separated list of distinguished name fields and values. For instance, "CN=www.server.com, OU=test, C=US, E=example@email.com". Common fields and their meanings are as follows:

| Field | Meaning |
| --- | --- |
| CN | Common Name. This is commonly a hostname like www.server.com. |
| O | Organization |
| OU | Organizational Unit |
| L | Locality |
| S | State |
| C | Country |
| E | Email Address |

If a field value contains a comma, it must be quoted.

 **Encoded** *string*
Default: ""

The certificate (PEM/Base64 encoded). This field is used to assign a specific certificate. The [Store](#Certificate_f_Store) and [Subject](#Certificate_f_Subject) fields also may be used to specify a certificate.

When [Encoded](#Certificate_f_Encoded) is set, a search is initiated in the current [Store](#Certificate_f_Store) for the private key of the certificate. If the key is found, [Subject](#Certificate_f_Subject) is updated to reflect the full subject of the selected certificate; otherwise, [Subject](#Certificate_f_Subject) is set to an empty string.

 **EncodedB** *byte []*
Default: ""

The certificate (PEM/Base64 encoded). This field is used to assign a specific certificate. The [Store](#Certificate_f_Store) and [Subject](#Certificate_f_Subject) fields also may be used to specify a certificate.

When [Encoded](#Certificate_f_Encoded) is set, a search is initiated in the current [Store](#Certificate_f_Store) for the private key of the certificate. If the key is found, [Subject](#Certificate_f_Subject) is updated to reflect the full subject of the selected certificate; otherwise, [Subject](#Certificate_f_Subject) is set to an empty string.

## Constructors

```text
public Certificate();
```

 Creates a instance whose properties can be set.

```text
public Certificate(string certificateFile);
```

 Opens * CertificateFile * and reads out the contents as an X.509 public key.

```text
public Certificate(byte[] encoded);
```

 Parses * Encoded * as an X.509 public key.

```text
public Certificate(CertStoreTypes storeType, string store, string storePassword, string subject);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a file containing the certificate store. * StorePassword * is the password used to protect the store.

 After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format.

```text
public Certificate(CertStoreTypes storeType, string store, string storePassword, string subject, string configurationString);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a file containing the certificate store. * StorePassword * is the password used to protect the store.

 * ConfigurationString * is a newline-separated list of name-value pairs that may be used to modify the default behavior. Possible values include "PersistPFXKey", which shows whether or not the PFX key is persisted after performing operations with the private key. This correlates to the PKCS12_NO_PERSIST_KEY CryptoAPI option. The default value is True (the key is persisted). "Thumbprint" - an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load. When specified, this value is used to select the certificate in the store. This is applicable to the * cstUser * , * cstMachine * , * cstPublicKeyFile * , and * cstPFXFile * store types. "UseInternalSecurityAPI" shows whether the platform (default) or the internal security API is used when performing certificate-related operations.

 After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format.

```text
public Certificate(CertStoreTypes storeType, string store, string storePassword, byte[] encoded);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a file containing the certificate store. * StorePassword * is the password used to protect the store.

 After the store has been successfully opened, the component will load * Encoded * as an X.509 certificate and search the opened store for a corresponding private key.

```text
public Certificate(CertStoreTypes storeType, byte[] store, string storePassword, string subject);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a byte array containing the certificate data. * StorePassword * is the password used to protect the store.

 After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format.

```text
public Certificate(CertStoreTypes storeType, byte[] store, string storePassword, string subject, string configurationString);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a byte array containing the certificate data. * StorePassword * is the password used to protect the store.

 After the store has been successfully opened, the component will attempt to find the certificate identified by * Subject * . This can be either a complete or a substring match of the X.509 certificate's subject Distinguished Name (DN). The * Subject * parameter can also take an MD5, SHA-1, or SHA-256 thumbprint of the certificate to load in a "Thumbprint=value" format.

```text
public Certificate(CertStoreTypes storeType, byte[] store, string storePassword, byte[] encoded);
```

 * StoreType * identifies the type of certificate store to use. See for descriptions of the different certificate stores. * Store * is a byte array containing the certificate data. * StorePassword * is the password used to protect the store.

 After the store has been successfully opened, the component will load * Encoded * as an X.509 certificate and search the opened store for a corresponding private key.

# Firewall Type

The firewall the component will connect through.

## Remarks

When connecting through a firewall, this type is used to specify different properties of the firewall, such as the firewall [Host](#Firewall_f_Host) and the [FirewallType](#Firewall_f_FirewallType).

The following fields are available:

- [AutoDetect](#Firewall_f_AutoDetect)

- [FirewallType](#Firewall_f_FirewallType)

- [Host](#Firewall_f_Host)

- [Password](#Firewall_f_Password)

- [Port](#Firewall_f_Port)

- [User](#Firewall_f_User)

## Fields

 **AutoDetect** *bool*
Default: False

Whether to automatically detect and use firewall system settings, if available.

 **FirewallType** *FirewallTypes*
Default: 0

The type of firewall to connect through. The applicable values are as follows:

|  |  |
| --- | --- |
| fwNone (0) | No firewall (default setting). |
| fwTunnel (1) | Connect through a tunneling proxy. [Port](#Firewall_f_Port) is set to 80. |
| fwSOCKS4 (2) | Connect through a SOCKS4 Proxy. [Port](#Firewall_f_Port) is set to 1080. |
| fwSOCKS5 (3) | Connect through a SOCKS5 Proxy. [Port](#Firewall_f_Port) is set to 1080. |
| fwSOCKS4A (10) | Connect through a SOCKS4A Proxy. [Port](#Firewall_f_Port) is set to 1080. |

 **Host** *string*
Default: ""

The name or IP address of the firewall (optional). If a [Host](#Firewall_f_Host) is given, the requested connections will be authenticated through the specified firewall when connecting.

If this field is set to a Domain Name, a DNS request is initiated. Upon successful termination of the request, this field is set to the corresponding address. If the search is not successful, the component throws an exception.

 **Password** *string*
Default: ""

A password if authentication is to be used when connecting through the firewall. If [Host](#Firewall_f_Host) is specified, the [User](#Firewall_f_User) and [Password](#Firewall_f_Password) fields are used to connect and authenticate to the given firewall. If the authentication fails, the component throws an exception.

 **Port** *int*
Default: 0

The Transmission Control Protocol (TCP) port for the firewall [Host](#Firewall_f_Host). See the description of the [Host](#Firewall_f_Host) field for details.

NOTE: This field is set automatically when [FirewallType](#Firewall_f_FirewallType) is set to a valid value. See the description of the [FirewallType](#Firewall_f_FirewallType) field for details.

 **User** *string*
Default: ""

A username if authentication is to be used when connecting through a firewall. If [Host](#Firewall_f_Host) is specified, this field and the [Password](#Firewall_f_Password) field are used to connect and authenticate to the given [Firewall](#firewall-type). If the authentication fails, the component throws an exception.

## Constructors

```text
public Firewall();
```

# PDFAttachment Type

The file being attached to the PDF document.

## Remarks

This type contains information about the file that is being attached to the document.

The following fields are available:

- [ContentType](#PDFAttachment_f_ContentType)

- [CreationDate](#PDFAttachment_f_CreationDate)

- [Data](#PDFAttachment_f_Data)

- [Description](#PDFAttachment_f_Description)

- [FileName](#PDFAttachment_f_FileName)

- [InputStream](#PDFAttachment_f_InputStream)

- [ModificationDate](#PDFAttachment_f_ModificationDate)

- [Name](#PDFAttachment_f_Name)

- [OutputStream](#PDFAttachment_f_OutputStream)

- [Size](#PDFAttachment_f_Size)

## Fields

 **ContentType** *string*
Default: ""

The content type of the attachment.

 **CreationDate** *string*
Default: ""

The creation date of the attachment.

 **Data** *string*
Default: ""

The raw data of the attachment.

If [OutputStream](#PDFAttachment_f_OutputStream) is not set to a valid stream, the component writes to this field when an empty string is passed to SaveAttachment.

 **DataB** *byte []*
Default: ""

The raw data of the attachment.

If [OutputStream](#PDFAttachment_f_OutputStream) is not set to a valid stream, the component writes to this field when an empty string is passed to SaveAttachment.

 **Description** *string*
Default: ""

A textual description of the attachment.

 **FileName** *string*
Default: ""

The path and filename of the attachment.

 **InputStream** *System.IO.Stream*
Default: ""

A stream containing the attachment.

If this field is set to a valid stream, the component attaches the data from the stream as the current attachment.

 **ModificationDate** *string*
Default: ""

The date and time of the file's last modification.

 **Name** *string*
Default: ""

The name of the attachment.

 **OutputStream** *System.IO.Stream*
Default: ""

The stream to write the attachment to.

If this field is set to a valid stream, the component writes to the stream when an empty string is passed to SaveAttachment.

 **Size** *long (read-only)*
Default: 0

The attachment's size in bytes.

## Constructors

```text
public PDFAttachment();
```

```text
public PDFAttachment(string fileName);
```

```text
public PDFAttachment(string fileName, string description);
```

```text
public PDFAttachment(byte[] data, string name, string description);
```

```text
public PDFAttachment(System.IO.Stream inputStream, string name, string description);
```

# PDFSignature Type

A container for PDF signature details.

## Remarks

This type contains details about the signature. Use it to read information about the signature when processing it.

The following fields are available:

- [AuthorName](#PDFSignature_f_AuthorName)

- [ChainValidationDetails](#PDFSignature_f_ChainValidationDetails)

- [ChainValidationResult](#PDFSignature_f_ChainValidationResult)

- [ClaimedSigningTime](#PDFSignature_f_ClaimedSigningTime)

- [CoverageEndsAt](#PDFSignature_f_CoverageEndsAt)

- [HashAlgorithm](#PDFSignature_f_HashAlgorithm)

- [Profile](#PDFSignature_f_Profile)

- [Reason](#PDFSignature_f_Reason)

- [SignatureType](#PDFSignature_f_SignatureType)

- [SignerCertIndex](#PDFSignature_f_SignerCertIndex)

- [TimestampCertIndex](#PDFSignature_f_TimestampCertIndex)

- [Timestamped](#PDFSignature_f_Timestamped)

- [ValidatedSigningTime](#PDFSignature_f_ValidatedSigningTime)

- [ValidationResult](#PDFSignature_f_ValidationResult)

- [WidgetHeight](#PDFSignature_f_WidgetHeight)

- [WidgetOffsetX](#PDFSignature_f_WidgetOffsetX)

- [WidgetOffsetY](#PDFSignature_f_WidgetOffsetY)

- [WidgetPages](#PDFSignature_f_WidgetPages)

- [WidgetWidth](#PDFSignature_f_WidgetWidth)

## Fields

 **AuthorName** *string (read-only)*
Default: ""

The human-readable name of the signer.

 **ChainValidationDetails** *int (read-only)*
Default: 0

The details of the certificate chain validation outcome. They may often suggest the reasons that contributed to the overall validation result in [ChainValidationResult](#PDFSignature_f_ChainValidationResult).

The value of this field is a bitmask of the following flags:

|  |  |
| --- | --- |
| 0x001 (cvdRevoked) | One or more certificates are revoked. |
| 0x002 (cvdExpiredOrNotYetValid) | One or more certificates are expired or not yet valid. |
| 0x004 (cvdUnknownCA) | A CA certificate for one or more certificates has not been found, is not trusted, or has a wrong public key (chain incomplete). |
| 0x008 (cvdPolicyViolated) | One of the CA certificates is not authorized to act as a CA, a mandatory key usage is not enabled in one of the chain certificates, or a weak algorithm is used in one of the certificates or revocation elements. |
| 0x010 (cvdRevocationCheckFailed) | One or more CRLs or OCSP responses could not be verified. |
| 0x020 (cvdBlocked) | One or more certificates are blocked. |
| 0x040 (cvdFailure) | General validation failure. |

Subscribe to the [Log](#log-event-pdfsign-component) event to access the detailed validation log. This field is also available as a parameter of the [SignatureProcessed](#signatureprocessed-event-pdfsign-component) event.

 **ChainValidationResult** *ChainValidationResults (read-only)*
Default: 0

The outcome of the certificate chain validation routine.

Possible values are:

|  |  |
| --- | --- |
| 0 (cvrUnknown - default) | Chain validity is unknown. |
| 1 (cvrValid) | The chain is valid. |
| 2 (cvrValidButUntrusted) | The chain is valid, but the root certificate is not trusted. |
| 3 (cvrInvalid) | The chain is not valid (some of the certificates are revoked, expired, or contain an invalid signature). |
| 4 (cvrCantBeEstablished) | The validity of the chain cannot be established because of missing or unavailable validation information (certificates, CRLs, or OCSP responses). |

Subscribe to the [Log](#log-event-pdfsign-component) event to access the detailed validation log. This field is also available as a parameter of the [SignatureProcessed](#signatureprocessed-event-pdfsign-component) event.

 **ClaimedSigningTime** *string (read-only)*
Default: ""

The signature's creation time in UTC.

Use this field to get the signature creation time from the signer's computer. Note that the claimed time, unlike [ValidatedSigningTime](#PDFSignature_f_ValidatedSigningTime), does not originate from a trusted TSA and may be forged or wrong.

 **CoverageEndsAt** *int (read-only)*
Default: 0

The byte offset in the PDF file where the signature coverage ends.

PDF generators often use incremental updates to make changes in documents. This may result in the signature only covering a part of the document (one of the past revisions), but not the subsequent changes.

Use this field to identify the offset where the signature coverage ends. One option is to compare it to the length of the whole document to ensure that the signature covers the entire document. Alternatively, use [GetSignedVersion](PDFVerify.md#PDFVerify_m_GetSignedVersion) to extract the exact revision that was signed.

A value of *0* indicates that the component could not determine the coverage offset.

 **HashAlgorithm** *string (read-only)*
Default: "SHA256"

The hash algorithm that was used for signing.

Possible values are:

- SHA1
- SHA224
- SHA256
- SHA384
- SHA512
- MD5

 **Profile** *PDFSignatureProfiles (read-only)*
Default: 0

The pre-defined PAdES profile that was applied when creating the signature, as defined by ETSI.

Advanced signatures come in many variants, and they are often defined by parties that need to process them or by local standards. Profiles are sets of pre-defined configurations that correspond to particular signature variants.

Possible values are:

|  |  |
| --- | --- |
| 0 (pfNone - default) | No profile |
| 1 (pfBaselineB) | PAdES B-B profile |
| 2 (pfBaselineT) | PAdES B-T profile |
| 3 (pfBaselineLT) | PAdES B-LT profile |
| 4 (pfBaselineLTA) | PAdES B-LTA profile |

Note that when verifying a signature, the LTV modifier may be affected by the validation settings. These include [OfflineMode](PDFVerify.md#PDFVerify_p_OfflineMode) (set it to *true* to obtain the clean LTV capability) and [CacheRevocationInfo](PDFVerify.md#CacheRevocationInfo) (set it to *false* to prevent earlier validations from affecting the current validation).

 **Reason** *string (read-only)*
Default: ""

The reason for signing.

 **SignatureType** *PDFSignatureTypes (read-only)*
Default: 0

The type of the signature that was created.

Possible values are:

|  |  |
| --- | --- |
| 0 (stLegacy - default) | Legacy Adobe signature (adbe.pkcs7.detached) |
| 1 (stAdvanced) | PAdES-compliant signature (ETSI.CAdES.detached) |
| 2 (stDTS) | Document timestamp (ETSI.RFC3161) |
| 3 (stEmptyField) | Empty signature field (signature placeholder) |

 **SignerCertIndex** *int (read-only)*
Default: -1

The index of the signer certificate in the [DocumentCerts](#documentcerts-property-pdfsign-component) collection.

 **TimestampCertIndex** *int (read-only)*
Default: -1

The index of the timestamping certificate in the [DocumentCerts](#documentcerts-property-pdfsign-component) collection (if applicable).

 **Timestamped** *bool (read-only)*
Default: False

Whether the signature contains an embedded timestamp.

 **ValidatedSigningTime** *string (read-only)*
Default: ""

The certified signing time in UTC.

Use this field to obtain the signing time as certified by a timestamp from a trusted timestamping authority. This field is only non-empty if there is a valid timestamp included in the signature.

Note that the validated time, unlike [ClaimedSigningTime](#PDFSignature_f_ClaimedSigningTime), is the trusted signing time.

 **ValidationResult** *SignatureValidationResults (read-only)*
Default: 0

The outcome of the cryptographic signature validation.

Possible values are:

|  |  |
| --- | --- |
| 0 (svrUnknown - default) | Signature validity is unknown. |
| 1 (svrValid) | The signature is valid. |
| 2 (svrCorrupted) | The signature is corrupted. |
| 3 (svrSignerNotFound) | Failed to acquire the signing certificate. The signature cannot be validated. |
| 4 (svrFailure) | General failure. |

This field is also available as the *SignatureValidationResult* parameter of the [SignatureProcessed](#signatureprocessed-event-pdfsign-component) event.

 **WidgetHeight** *string (read-only)*
Default: "70"

The height of the signature widget in points.

 **WidgetOffsetX** *string (read-only)*
Default: "0"

The signature widget offset from the left-hand page border in points.

 **WidgetOffsetY** *string (read-only)*
Default: "0"

The signature widget offset from the bottom page border in points.

 **WidgetPages** *string (read-only)*
Default: ""

The pages that the signature and its widget are placed on.

 **WidgetWidth** *string (read-only)*
Default: "70"

The width of the signature widget in points.

## Constructors

```text
public PDFSignature();
```

# Proxy Type

The proxy the component will connect to.

## Remarks

When connecting through a proxy, this type is used to specify different properties of the proxy, such as the [Server](#Proxy_f_Server) and the [AuthScheme](#Proxy_f_AuthScheme).

The following fields are available:

- [AuthScheme](#Proxy_f_AuthScheme)

- [AutoDetect](#Proxy_f_AutoDetect)

- [Password](#Proxy_f_Password)

- [Port](#Proxy_f_Port)

- [Server](#Proxy_f_Server)

- [SSL](#Proxy_f_SSL)

- [User](#Proxy_f_User)

## Fields

 **AuthScheme** *ProxyAuthSchemes*
Default: 0

The type of authorization to perform when connecting to the proxy. This is used only when the [User](#Proxy_f_User) and [Password](#Proxy_f_Password) fields are set.

[AuthScheme](#Proxy_f_AuthScheme) should be set to authNone (3) when no authentication is expected.

By default, [AuthScheme](#Proxy_f_AuthScheme) is authBasic (0), and if the [User](#Proxy_f_User) and [Password](#Proxy_f_Password) fields are set, the component will attempt basic authentication.

If [AuthScheme](#Proxy_f_AuthScheme) is set to authDigest (1), digest authentication will be attempted instead.

If [AuthScheme](#Proxy_f_AuthScheme) is set to authProprietary (2), then the authorization token will not be generated by the component. Look at the configuration file for the component being used to find more information about manually setting this token.

If [AuthScheme](#Proxy_f_AuthScheme) is set to authNtlm (4), NTLM authentication will be used.

For security reasons, setting this field will clear the values of [User](#Proxy_f_User) and [Password](#Proxy_f_Password).

 **AutoDetect** *bool*
Default: False

Whether to automatically detect and use proxy system settings, if available. The default value is *false*.

 **Password** *string*
Default: ""

A password if authentication is to be used for the proxy.

If [AuthScheme](#Proxy_f_AuthScheme) is set to Basic Authentication, the [User](#Proxy_f_User) and [Password](#Proxy_f_Password) fields are Base64 encoded and the proxy authentication token will be generated in the form *Basic [encoded-user-password]*.

If [AuthScheme](#Proxy_f_AuthScheme) is set to Digest Authentication, the [User](#Proxy_f_User) and [Password](#Proxy_f_Password) fields are used to respond to the Digest Authentication challenge from the server.

If [AuthScheme](#Proxy_f_AuthScheme) is set to NTLM Authentication, the [User](#Proxy_f_User) and [Password](#Proxy_f_Password) fields are used to authenticate through NTLM negotiation.

 **Port** *int*
Default: 80

The Transmission Control Protocol (TCP) port for the proxy [Server](#Proxy_f_Server) (default 80). See the description of the [Server](#Proxy_f_Server) field for details.

 **Server** *string*
Default: ""

If a proxy [Server](#Proxy_f_Server) is given, then the HTTP request is sent to the proxy instead of the server otherwise specified.

If the [Server](#Proxy_f_Server) field is set to a domain name, a DNS request is initiated. Upon successful termination of the request, the [Server](#Proxy_f_Server) field is set to the corresponding address. If the search is not successful, an error is returned.

 **SSL** *ProxySSLTypes*
Default: 0

When to use a Secure Sockets Layer (SSL) for the connection to the proxy. The applicable values are as follows:

|  |  |
| --- | --- |
| psAutomatic (0) | Default setting. If the URL is an https URL, the component will use the psTunnel option. If the URL is an http URL, the component will use the psNever option. |
| psAlways (1) | The connection is always SSL-enabled. |
| psNever (2) | The connection is not SSL-enabled. |
| psTunnel (3) | The connection is made through a tunneling (HTTP) proxy. |

 **User** *string*
Default: ""

A username if authentication is to be used for the proxy.

If [AuthScheme](#Proxy_f_AuthScheme) is set to Basic Authentication, the [User](#Proxy_f_User) and [Password](#Proxy_f_Password) fields are Base64 encoded and the proxy authentication token will be generated in the form *Basic [encoded-user-password]*.

If [AuthScheme](#Proxy_f_AuthScheme) is set to Digest Authentication, the [User](#Proxy_f_User) and [Password](#Proxy_f_Password) fields are used to respond to the Digest Authentication challenge from the server.

If [AuthScheme](#Proxy_f_AuthScheme) is set to NTLM Authentication, the [User](#Proxy_f_User) and [Password](#Proxy_f_Password) fields are used to authenticate through NTLM negotiation.

## Constructors

```text
public Proxy();
```

```text
public Proxy(string server, int port);
```

```text
public Proxy(string server, int port, string user, string password);
```

# Config Settings ([PDFSign](#pdfsign-component) Component)

 The component accepts one or more of the following *configuration settings*. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these *internal properties* is provided through the [Config](#config-method-pdfsign-component) method.

### PDFSign Config Settings

**AFRelationship[Key]**: The value of the AFRelationship key for the attachment.This setting specifies the value of the AFRelationship key for the attachment. This key in the file specification dictionary expresses the relationship between the attachment and the document, and it must be set for each attachment added to PDF/A-3 documents. *Key* is either the index of the attachment in the [Attachments](#attachments-property-pdfsign-component) collection or the [Name](#PDFAttachment_f_Name) of the attachment.

**CacheRevocationInfo**: Whether to cache revocation information.This setting specifies whether the component caches revocation information. If set to *true*, the component preserves downloaded CRLs and OCSP responses in memory and reuses them in subsequent chain validations. If set to *false*, the component always collects revocation information from scratch (when applicable). The default value is *true*.

**CloseInputStreamAfterProcessing**: Whether to close the input stream after processing.This setting determines whether the input stream specified in [SetInputStream](#setinputstream-method-pdfsign-component) will be closed after processing is complete. The default value is *true*.

**CloseOutputStreamAfterProcessing**: Whether to close the output stream after processing.This setting determines whether the output stream specified in [SetOutputStream](#setoutputstream-method-pdfsign-component) will be closed after processing is complete. The default value is *true*.

**CompressDSS**: Whether to compress content in the DSS dictionary.This setting determines whether content in the DSS dictionary will be compressed. The default value is *true*.

**ContactInfo[Index]**: The signer's contact information.This indexed setting specifies the signer's contact information for a signature. *Index* is the index of the signature in the [Signatures](#signatures-property-pdfsign-component) collection. When creating a new signature, use *-1* as the *Index*.

**CustomProfile**: A pre-defined custom profile to apply when creating the signature.This setting specifies a pre-defined custom profile to apply when creating the signature. Possible values are:

|  |  |
| --- | --- |
| BR.AD_RB_v1_0 | Brazilian signature with Basic Reference (AD-RB) version 1.0 |
| BR.AD_RB_v1_1 | Brazilian signature with Basic Reference (AD-RB) version 1.1 |
| BR.AD_RT_v1_0 | Brazilian signature with Time Reference (AD-RT) version 1.0 |
| BR.AD_RT_v1_1 | Brazilian signature with Time Reference (AD-RT) version 1.1 |
| BR.AD_RC_v1_1 | Brazilian signature with Complete References (AD-RC) version 1.1 |
| BR.AD_RC_v1_2 | Brazilian signature with Complete References (AD-RC) version 1.2 |
| BR.AD_RA_v1_1 | Brazilian signature with References for Archiving (AD-RA) version 1.1 |
| BR.AD_RA_v1_2 | Brazilian signature with References for Archiving (AD-RA) version 1.2 |

**CustomSignedAttributes**: The custom signed attributes to be added to the inner CMS.This setting specifies a CRLF-separated list of custom signed attributes that are added to the inner CMS when [Sign](#sign-method-pdfsign-component) is called. Each attribute must be specified as a *name=value* pair containing an OID followed by an ASN.1-encoded attribute value. For example:

```csharp
pdfsign.Config("CustomSignedAttributes=1.2.3.4.5=04084142434445464748\r\n1.2.3.4.7=02020404");
```

**EnforcePDFA**: Whether to enforce PDF/A compliance.This setting specifies whether the component enforces PDF/A compliance when operating on the document. If set to *true*, [PDFALevel](#PDFALevel) and [PDFAPolicy](#PDFAPolicy) are used to establish the level of PDF/A compliance to apply. The default value is *false*.

**ExtraSpace**: The number of extra zero bytes to allocate in the document behind the signature.This setting specifies the number of extra zero bytes to allocate in the document behind the signature. The allocated space can be used in the future to place a timestamp.

**FallbackFont**: The fallback font.This setting specifies the font that the component uses if it cannot find the intended font on the local system. In PDF/A, fonts must be embedded into the document, so this setting can be useful when text must be added but no font is available.

**FilterName[Index]**: The signature filter name.This indexed setting specifies the signature filter name. The default value is *nsoftware.SecurePDF*.

*Index* is the index of the signature in the [Signatures](#signatures-property-pdfsign-component) collection. When creating a new signature, use *-1* as the *Index*. If set to *PBAD_PAdES*, the component creates a PBAD.PAdES-compatible signature.

**FontPaths**: The font search paths.This setting specifies a CRLF-separated list of directories where the component searches for additional TrueType font files. It is used when resolving a TrueType font specified in the *FontName* widget property without a full file path.

Each entry is interpreted as a directory path used during font lookup. To use a specific TrueType font file, either specify its filename and include the containing directory in this setting, or specify the full file path in the *FontName* widget property.

The default value is the system font search paths. These paths are platform-dependent:

|  |  |
| --- | --- |
| Windows | %windir%\Fonts and %LOCALAPPDATA%\Microsoft\Windows\Fonts |
| macOS and iOS | /System/Library/Fonts/, /Library/Fonts/, and ~/Library/Fonts/ |
| Linux | Directories listed by dir entries in /etc/fonts/fonts.conf and /usr/local/etc/fonts/fonts.conf |
| Android | /system/fonts |

On Windows, the .NET and Java editions obtain these locations through the runtime APIs or the *windir*, *SystemRoot*, and *LOCALAPPDATA* environment variables.

To use custom directories together with the default system locations, include both to prevent the current search path list from being replaced. For example:

```csharp
string fontPaths = pdfsign.Config("FontPaths");
fontPaths += @"\r\nC:\Fonts";
pdfsign.Config("FontPaths=" + fontPaths);
```

**FullSignatureName[Index]**: The full name of the signature field.This indexed setting specifies the full name of the signature field. It is an internal identifier of a signature (such as *Signature1*) and is not meant to be human-readable.

*Index* is the index of the signature in the [Signatures](#signatures-property-pdfsign-component) collection. When creating a new signature, use *-1* as the *Index*.

**HTTPRetryCount**: The number of HTTP request retries.This setting specifies the number of times to retry an HTTP request. It can be useful in the case of timestamping or CRL/OCSP retrieval failures.

**HTTPRetryInterval**: A time interval to apply between HTTP request retries.This setting specifies the time interval (in seconds) to apply between successive HTTP request retries. It can be useful in the case of timestamping or CRL/OCSP retrieval failures.

**IncludeRevocationInfo**: Whether to include revocation information in the document.This setting specifies whether and where revocation information is included in the document when [Sign](#sign-method-pdfsign-component) or [Update](#update-method-pdfsign-component) is called. Its value should be provided as a bitmask of the following flags:

|  |  |
| --- | --- |
| 0x001 (rilAutomatic) | Include revocation information in either the DSS dictionary or the adbe-revocationInfoArchival signature attribute depending on the [SignatureType](#signaturetype-property-pdfsign-component). |
| 0x002 (rilDSS) | Include revocation information in the DSS dictionary. |
| 0x004 (rilAdbeAttribute) | Include revocation information in the adbe-revocationInfoArchival signature attribute. |

The default value is *0x001*, meaning the component saves revocation information in the DSS dictionary for advanced (PAdES) signatures, and in the adbe-revocationInfoArchival signature attribute for legacy signatures. This complies with the respective standards.

**IncludeSigningChain**: Whether to include the full signing chain in the signature.This setting specifies whether and how the full signing certificate chain is included in the signature. Possible values are:

|  |  |
| --- | --- |
| 0 | Do not include the signing chain in the signature. |
| 1 (default) | Attempt to build the signing chain automatically, and if successful, include it in the signature. |
| 2 | Include the contents of [KnownCerts](#knowncerts-property-pdfsign-component) in the signature. |

**LogLevel**: The level of detail that is logged.This setting controls the level of detail that is logged through the [Log](#log-event-pdfsign-component) event. Possible values are:

|  |  |
| --- | --- |
| 0 (None) | No messages are logged. |
| 1 (Info - default) | Informational events such as the basics of the chain validation procedure are logged. |
| 2 (Verbose) | Detailed data such as HTTP requests are logged. |
| 3 (Debug) | Debug data including the full chain validation procedure are logged. |

**OwnerPassword**: The owner password to decrypt the document with.This setting is used to provide the document owner password for decryption. Though it may be different from [Password](#password-property-pdfsign-component), most implementations use the same value for both.

**PDFALevel**: The PDF/A conformance level to enforce.This setting specifies the desired PDF/A conformance level that the component attempts to enforce when [EnforcePDFA](#EnforcePDFA) is set to *true*. Possible values are:

|  |  |
| --- | --- |
| 1 | PDF/A-1 |
| 2 | PDF/A-2 |
| 3 (default) | PDF/A-3 |

**PDFAPolicy**: The PDF/A policy to follow.This setting specifies the PDF/A policy the component follows when [EnforcePDFA](#EnforcePDFA) is set to *true*. Possible values are:

|  |  |
| --- | --- |
| Default | Maps to Preserve. |
| Preserve | Keep existing document features and only write PDF/A-compliant pieces. If the component needs to write a non-compliant piece, it throws an exception. |
| Enforce | Preserve PDF/A-compliant pieces and attempt to fix violations in the original document. |

**Permissions**: The document permissions associated with the encryption.This setting returns the permissions protected by this encryption. The PDF specification expects applications to comply with these permissions when handling encrypted documents, but note that it is a policy-like requirement rather than an enforcement.

This setting is read-only. Its value is a bitmask of the following flags:

|  |  |
| --- | --- |
| 0x001 (pepAnnotations) | Annotating is allowed. |
| 0x002 (pepAssemble) | Assembling a new document on the basis of the processed one is allowed. |
| 0x004 (pepExtract) | Extraction/copying of the pictures and text from the document is allowed. |
| 0x008 (pepExtractAcc) | Content extraction is allowed for accessibility purposes only. |
| 0x010 (pepFillInForms) | Filling in forms is allowed. |
| 0x020 (pepHighQualityPrint) | High quality printing is allowed. |
| 0x040 (pepLowQualityPrint) | Low quality printing is allowed. |
| 0x080 (pepModify) | Modifications are allowed. |

**PolicyHash**: The signature policy hash value.This setting specifies the hash of the external signature policy document. The hash is calculated by the policy author when the policy is created, and it is included in the policy file. This setting must be set, together with [PolicyHashAlgorithm](#PolicyHashAlgorithm) and [PolicyId](#PolicyId), in order to create an EPES signature.

**PolicyHashAlgorithm**: The algorithm that was used to calculate the signature policy hash.This setting specifies the algorithm that was used to calculate the signature policy hash. It must be set, together with [PolicyHash](#PolicyHash) and [PolicyId](#PolicyId), in order to create an EPES signature.

**PolicyId**: The policy Id to be included in the signature.This setting specifies the signature policy Id to be included in the signature. It must be set, together with [PolicyHash](#PolicyHash) and [PolicyHashAlgorithm](#PolicyHashAlgorithm), in order to create an EPES signature.

**PreferEmbeddedRevocationInfo**: Whether to prioritize revocation information that is embedded into the document.This setting specifies whether the component uses revocation information that is embedded into the document when checking revocation status. If set to *true*, the component does not download CRLs or OCSP responses from online sources unnecessarily. If set to *false* or no embedded revocation information is present, the component retrieves it as normal based on the value of [RevocationCheck](#revocationcheck-property-pdfsign-component). The default value is *true*.

**RemoteSignatureData**: The hex-encoded signature data obtained from a remote signing engine.This setting specifies the hex-encoded signature data obtained from a remote signing engine. Use it to pass the [RemoteSignatureDigest](#RemoteSignatureDigest) back to the component (after it has been processed appropriately and signed) to complete the signature.

NOTE: This setting is deprecated. Please use the [RemoteSignatureData](#remotesignaturedata-property-pdfsign-component) property instead.

**RemoteSignatureDigest**: The hex-encoded digest to be signed remotely.This setting returns the hex-encoded digest that should be passed to a remote signing engine to be signed. Note that in the PKCS#1 method, this value is the raw data of the PKCS#7 signed-attributes field, whereas in the PKCS#7 method, it is the document hash. This setting is read-only.

NOTE: This setting is deprecated. Please use the [RemoteSignatureDigest](#remotesignaturedigest-property-pdfsign-component) property instead.

**RemoteSignatureMethod**: The remote signing method.This setting specifies whether and how the new signature is intended to be created remotely. If set to *pkcs1* or *pkcs7* before [Sign](#sign-method-pdfsign-component) is called, the component does not perform the low-level signing operation itself but instead delegates it to an external or remote signing engine. Possible values are:

|  |  |
| --- | --- |
| none (default) | Do not create the signature remotely. |
| pkcs1 | Create the signature remotely using the PKCS#1 signing method. The component builds the PKCS#7 structure itself and populates [RemoteSignatureDigest](#RemoteSignatureDigest) with the raw data of the signed-attributes field. Note that [SigningCert](#signingcert-property-pdfsign-component) must be set in order to use this option. |
| pkcs7 | Create the signature remotely using the PKCS#7 signing method. The component populates [RemoteSignatureDigest](#RemoteSignatureDigest) with the document hash, and the remote signer is expected to build the PKCS#7 structure. Use this option if the signing certificate is not available. |
| pkcs7sign | Sign the digest generated earlier using the PKCS#7 method and produce the corresponding PKCS#7 structure. The input is expected to contain an unencoded binary message digest, and the output is a binary PKCS#7 object. Unlike the other options, this is a one-pass method. Note that no PDF data is involved in either input or output. |

NOTE: This setting is deprecated. Please use the [RemoteSignatureMethod](#remotesignaturemethod-property-pdfsign-component) property instead.

**RevisionOffsets**: The offsets of the document revisions.This setting returns a comma-separated list of the byte offsets of all the revisions in the document. It may be used to obtain the number of revisions or extract a particular revision. This setting is read-only.

**SaveChanges**: Whether to save changes made to the document.This setting specifies whether and how changes made to the PDF document are saved when [Close](#close-method-pdfsign-component) is called. Possible values are:

|  |  |
| --- | --- |
| 0 | Discard all changes. |
| 1 | Save the document to [OutputFile](#outputfile-property-pdfsign-component), [OutputData](#outputdata-property-pdfsign-component), or the stream set in [SetOutputStream](#setoutputstream-method-pdfsign-component), even if it has not been modified. |
| 2 (default) | Save the document to [OutputFile](#outputfile-property-pdfsign-component), [OutputData](#outputdata-property-pdfsign-component), or the stream set in [SetOutputStream](#setoutputstream-method-pdfsign-component), but only if it has been modified. |

**SignatureData[Index]**: The hex-encoded representation of the underlying PKCS#7/CMS signature container.This indexed setting returns the hex-encoded representation of the underlying PKCS#7/CMS signature container, or the timestamp token for document timestamps. *Index* is the index of the signature in the [Signatures](#signatures-property-pdfsign-component) collection. This setting is read-only.

**SystemFontNames**: The system font names.This setting returns a CRLF-separated list of system TrueType font names that are supported by the component. This setting is read-only.

**TempPath**: The location where temporary files are stored.This setting specifies an absolute path to the location on disk where temporary files are stored. It can be useful to reduce memory usage.

**TimestampHashAlgorithm**: A specific hash algorithm for use with the timestamping service.This setting specifies a different hash algorithm to use for the timestamp. In its default configuration, the component uses the same hash algorithm for the main signature and any associated timestamps.

**TSATLSClientCertStore**: The TLS client certificate store to search.This setting specifies the TLS client certificate store to search when the TSA requests TLS client authentication. Designations of certificate stores are platform-dependent. The following designations are the most common User and Machine certificate stores in Windows:

|  |  |
| --- | --- |
| MY | A certificate store holding personal certificates with their associated private keys. |
| CA | Certifying authority certificates. |
| ROOT | Root certificates. |

 When [TSATLSClientCertStoreType](#TSATLSClientCertStoreType) is set to 2 (*cstPFXFile*), this setting must be set to the name of the file. When the type is set to 3 (*cstPFXBlob*), this setting must be set to the binary contents of a PFX file (i.e., a PKCS#12 certificate store). If the store is password-protected, specify the password in [TSATLSClientCertStorePassword](#TSATLSClientCertStorePassword).

**TSATLSClientCertStorePassword**: The password needed to open the TLS client certificate store.This setting specifies the password needed to open the TLS client certificate store when the TSA requests TLS client authentication.

**TSATLSClientCertStoreType**: The type of the TLS client certificate store.This setting specifies the type of the TLS client certificate store specified by [TSATLSClientCertStore](#TSATLSClientCertStore). The component supports both public and private keys in a variety of formats. When the *cstAuto* value is used, the component will automatically determine the type. This field can take one of the following values:

```csharp
sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11,
                               @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll",
                               "123456", // PIN
                               "CN=cert_subject");
sftp.SSHUser = "test";
sftp.SSHLogon("myhost", 22);
```

```csharp
certmgr.CertStoreType = CertStoreTypes.cstPKCS11;
certmgr.OnCertList += (s, e) => {
  secKeyBlob = e.CertEncoded;
};
certmgr.CertStore = @"C:\Program Files\OpenSC Project\OpenSC\pkcs11\opensc-pkcs11.dll";
certmgr.CertStorePassword = "123456"; // PIN
certmgr.ListStoreCertificates();

sftp.SSHCert = new Certificate(CertStoreTypes.cstPKCS11, secKeyBlob, "123456", "*");
sftp.SSHUser = "test";
sftp.SSHLogon("myhost", 22);
```

|  |  |
| --- | --- |
| 0 (cstUser - default) | For Windows, this specifies that the certificate store is a certificate store owned by the current user. NOTE: This store type is not available in Java. |
| 1 (cstMachine) | For Windows, this specifies that the certificate store is a machine store. NOTE: This store type is not available in Java. |
| 2 (cstPFXFile) | The certificate store is the name of a PFX (PKCS#12) file containing certificates. |
| 3 (cstPFXBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in PFX (PKCS#12) format. |
| 4 (cstJKSFile) | The certificate store is the name of a Java Key Store (JKS) file containing certificates. NOTE: This store type is only available in Java. |
| 5 (cstJKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in Java Key Store (JKS) format. NOTE: This store type is only available in Java. |
| 6 (cstPEMKeyFile) | The certificate store is the name of a PEM-encoded file that contains a private key and an optional certificate. |
| 7 (cstPEMKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a private key and an optional certificate. |
| 8 (cstPublicKeyFile) | The certificate store is the name of a file that contains a PEM- or DER-encoded public key certificate. |
| 9 (cstPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains a PEM- or DER-encoded public key certificate. |
| 10 (cstSSHPublicKeyBlob) | The certificate store is a string (binary or Base64-encoded) that contains an SSH-style public key. |
| 11 (cstP7BFile) | The certificate store is the name of a PKCS#7 file containing certificates. |
| 12 (cstP7BBlob) | The certificate store is a string (binary) representing a certificate store in PKCS#7 format. |
| 13 (cstSSHPublicKeyFile) | The certificate store is the name of a file that contains an SSH-style public key. |
| 14 (cstPPKFile) | The certificate store is the name of a file that contains a PPK (PuTTY Private Key). |
| 15 (cstPPKBlob) | The certificate store is a string (binary) that contains a PPK (PuTTY Private Key). |
| 16 (cstXMLFile) | The certificate store is the name of a file that contains a certificate in XML format. |
| 17 (cstXMLBlob) | The certificate store is a string that contains a certificate in XML format. |
| 18 (cstJWKFile) | The certificate store is the name of a file that contains a JWK (JSON Web Key). |
| 19 (cstJWKBlob) | The certificate store is a string that contains a JWK (JSON Web Key). |
| 21 (cstBCFKSFile) | The certificate store is the name of a file that contains a BCFKS (Bouncy Castle FIPS Key Store). NOTE: This store type is only available in Java and .NET. |
| 22 (cstBCFKSBlob) | The certificate store is a string (binary or Base64-encoded) representing a certificate store in BCFKS (Bouncy Castle FIPS Key Store) format. NOTE: This store type is only available in Java and .NET. |
| 23 (cstPKCS11) | The certificate is present on a physical security key accessible via a PKCS#11 interface. To use a security key, create a new [Certificate](#certificate-type) object and pass cstPKCS11 as the [StoreType](#Certificate_f_StoreType), the full path of the PKCS#11 DLL as the [Store](#Certificate_f_Store), and the PIN as the [StorePassword](#Certificate_f_StorePassword). Code Example. SSH Authentication with Security Key (without CertMgr): Alternatively, collect the necessary data using the [CertMgr](CertMgr.md#CertMgr) component by calling the [ListStoreCertificates](CertMgr.md#CertMgr_m_ListStoreCertificates) method after setting the corresponding properties accordingly. The certificate information returned in the [CertList](CertMgr.md#CertMgr_e_CertList) event's CertEncoded parameter may be saved for later use. When using a certificate obtained with this approach, pass the previously saved security key information as the [Store](#Certificate_f_Store) and set [StorePassword](#Certificate_f_StorePassword) to the PIN. Code Example. SSH Authentication with Security Key (with CertMgr): |
| 99 (cstAuto) | The store type is automatically detected from the input data. This setting may be used with both public and private keys and can detect any of the supported formats automatically. |

**TSATLSClientCertSubject**: The subject of the TLS client certificate.This setting specifies the subject of the TLS client certificate to use when the TSA requests TLS client authentication. When loading a certificate, the subject is used to locate the certificate in the store. If an exact match is not found, the store is searched for subjects containing the value of the setting. If a match is still not found, the setting is set to an empty string, and no certificate is selected.

The asterisk character (***) picks a random certificate in the certificate store.

The certificate subject is a comma-separated list of distinguished name fields and values. For instance, "CN=www.server.com, OU=test, C=US, E=example@email.com". Common fields and their meanings are as follows:

| Field | Meaning |
| --- | --- |
| CN | Common Name. This is commonly a hostname like www.server.com. |
| O | Organization |
| OU | Organizational Unit |
| L | Locality |
| S | State |
| C | Country |
| E | Email Address |

If a field value contains a comma, it must be quoted.

**UpdateIndex**: The index of the signature to update.This setting specifies the index of the signature in the [Signatures](#signatures-property-pdfsign-component) collection to be updated. The default value is *-1*, meaning the component updates the most recent signature.

**UsePSS**: Whether to use RSA-PSS during signing and verification.This setting specifies whether RSA-PSS is used when signing and verifying documents. The default value is *false*.

### Base Config Settings

**BuildInfo**: Information about the product's build.When queried, this setting will return a string containing information about the product's build.

**GUIAvailable**: Whether or not a message loop is available for processing events.In a GUI-based application, long-running blocking operations may cause the application to stop responding to input until the operation returns. The component will attempt to discover whether or not the application has a message loop and, if one is discovered, it will process events in that message loop during any such blocking operation.

In some non-GUI applications, an invalid message loop may be discovered that will result in errant behavior. In these cases, setting [GUIAvailable](#GUIAvailable) to *false* will ensure that the component does not attempt to process external events.

**LicenseInfo**: Information about the current license.When queried, this setting will return a string containing information about the license this instance of a component is using. It will return the following information:

- Product: The product the license is for.
- Product Key: The key the license was generated from.
- License Source: Where the license was found (e.g., RuntimeLicense, License File).
- License Type: The type of license installed (e.g., Royalty Free, Single Server).
- Last Valid Build: The last valid build number for which the license will work.

**MaskSensitiveData**: Whether sensitive data is masked in log messages.In certain circumstances it may be beneficial to mask sensitive data, like passwords, in log messages. Set this to *true* to mask sensitive data. The default is *true*.

**UseInternalSecurityAPI**: Whether or not to use the system security libraries or an internal implementation. When set to *false*, the component will use the system security libraries by default to perform cryptographic functions where applicable. In this case, calls to unmanaged code will be made. In certain environments, this is not desirable. To use a completely managed security implementation, set this setting to *true*.

Setting this configuration setting to *true* tells the component to use the internal implementation instead of using the system security libraries.

 On Windows, this setting is set to *false* by default. On Linux/macOS, this setting is set to *true* by default.

NOTE: This setting is static. The value set is applicable to all components used in the application.

When this value is set, the product's system dynamic link library (DLL) is no longer required as a reference, as all unmanaged code is stored in that file.

# Trappable Errors ([PDFSign](#pdfsign-component) Component)

### PDFSign Errors

|  |  |
| --- | --- |
| 801 | No timestamp server specified. |
| 802 | HTTP download failed. The error description contains the detailed message. |
| 803 | The document is not signed. |
| 810 | Unsupported image type. |
| 811 | Unsupported color space type. |
| 816 | Invalid signature. The error description contains the detailed message. |
| 827 | Invalid timestamp data. The error description contains the detailed message. |
| 829 | Bad signing certificate attribute. |
| 830 | Chain validation failed. The error description contains the detailed message. |
| 831 | Cannot sign data or update this type of signature. The error description contains the detailed message. |
| 833 | Trusted List processing error. The error description contains the detailed message. |
| 834 | Cannot parse Trusted List data. |
| 837 | Invalid revocation information. |
| 839 | Failed to process Trusted List. The error description contains the detailed message. |
| 843 | No signing certificate found. |
| 845 | Invalid signing certificate chain. The error description contains the detailed message. |
| 851 | Unsupported hash algorithm. |
| 855 | Invalid signature contents. |
| 856 | Invalid signature byte range. |
| 857 | Byte range does not cover the entire document. |
| 858 | Cannot sign and encrypt document with more than one signature. |
| 862 | Cannot timestamp encrypted document. |
| 863 | Cannot update encrypted document. |
| 865 | Signature is too large to fit in the allocated window. Please consider extending the window by assigning the number of bytes to add to the [ExtraSpace](#ExtraSpace) config before closing the document. |
| 866 | Not enough space to update signature. |
| 875 | Bad signature type (only PKCS#7/CMS signatures are supported by this handler). |
| 876 | Invalid decryption mode. |

### PDF Errors

|  |  |
| --- | --- |
| 804 | PDF decompression failed. |
| 805 | Cannot add entry to cross-reference table. |
| 806 | Unsupported field size. |
| 807 | Unsupported Encoding filter. |
| 808 | Unsupported predictor algorithm. |
| 809 | Unsupported document version. |
| 812 | Cannot read PDF file stream. |
| 813 | Cannot write to PDF file stream. |
| 814 | [OutputFile](#outputfile-property-pdfsign-component) already exists and [Overwrite](#overwrite-property-pdfsign-component) is false. |
| 815 | Invalid parameter. |
| 817 | Bad cross-reference entry. |
| 818 | Invalid object or generation number. |
| 819 | Invalid object stream. |
| 820 | Invalid stream dictionary. |
| 821 | Invalid AcroForm entry. |
| 822 | Invalid Root entry. |
| 823 | Invalid annotation. |
| 824 | The input document is empty. |
| 826 | OpenType font error. The error description contains the detailed message. |
| 828 | Invalid CMS data. The error description contains the detailed message. |
| 835 | Cannot change decryption mode for opened document. |
| 836 | Unsupported Date string. |
| 838 | Cryptographic error. The error description contains the detailed message. |
| 840 | [DecryptionCert](#decryptioncert-property-pdfsign-component) error. The error description contains the detailed message. |
| 841 | Encryption failed. The error description contains the detailed message. |
| 842 | No proper certificate for encryption found. |
| 846 | Unsupported revision. |
| 847 | Unsupported security handler SubFilter. |
| 848 | Failed to verify permissions. |
| 849 | Invalid password. |
| 850 | Invalid password information. |
| 852 | Unsupported encryption algorithm. |
| 859 | Cannot encrypt encrypted document. |
| 864 | Cannot modify document after signature update. |
| 868 | Cannot encrypt or decrypt object. |
| 869 | Invalid security handler information. |
| 870 | Invalid encrypted data. |
| 871 | Invalid block cipher padding. |
| 872 | Failed to reload signature. |
| 873 | Object is not encrypted. |
| 874 | Unexpected cipher information. |
| 877 | Invalid document. Bad document catalog. |
| 878 | Invalid document Id. |
| 880 | Invalid document. Invalid requirements dictionary. |
| 881 | Invalid linearization dictionary. |
| 882 | Invalid signature information. |
| 883 | Unsupported document format. |
| 890 | Unsupported feature. |
| 891 | Internal error. The error description contains the detailed message. |
| 892 | Unsupported color. |
| 893 | This operation is not supported for this PDF/A level. |
| 894 | Interactive features ([Action](#PDFField_f_Action)) are not supported by PDF/A. Set [EnforcePDFA](#EnforcePDFA) to false or clear the [Action](#PDFField_f_Action) property of the field. |
| 895 | Font file not found. |

### Parsing Errors

|  |  |
| --- | --- |
| 1001 | Bad object. |
| 1002 | Bad document trailer. |
| 1003 | Illegal stream dictionary. |
| 1004 | Illegal string. |
| 1005 | Indirect object expected. |
| 1007 | Invalid reference. |
| 1008 | Invalid reference table. |
| 1009 | Invalid stream data. |
| 1010 | Unexpected character. |
| 1011 | Unexpected EOF. |
| 1012 | Unexpected indirect object in cross-reference table. |
| 1013 | RDF object not found. |
| 1014 | Invalid RDF object. |
| 1015 | Cannot create element with unknown prefix. |
| 1021 | Invalid type in Root object list. |

The component may also return one of the following error codes, which are inherited from other components.

### HTTP Errors

|  |  |
| --- | --- |
| 118 | Firewall error. The error description contains the detailed message. |
| 143 | Busy executing current method. |
| 151 | HTTP protocol error. The error message has the server response. |
| 152 | No server specified in URL. |
| 153 | Specified URLScheme is invalid. |
| 155 | Range operation is not supported by server. |
| 156 | Invalid cookie index (out of range). |
| 301 | Interrupted. |
| 302 | Cannot open AttachedFile. |

The component may also return one of the following error codes, which are inherited from other components.

### TCPClient Errors

|  |  |
| --- | --- |
| 100 | You cannot change the RemotePort at this time. A connection is in progress. |
| 101 | You cannot change the RemoteHost (Server) at this time. A connection is in progress. |
| 102 | The RemoteHost address is invalid (0.0.0.0). |
| 104 | Already connected. If you want to reconnect, close the current connection first. |
| 106 | You cannot change the LocalPort at this time. A connection is in progress. |
| 107 | You cannot change the LocalHost at this time. A connection is in progress. |
| 112 | You cannot change [MaxLineLength](#MaxLineLength) at this time. A connection is in progress. |
| 116 | RemotePort cannot be zero. Please specify a valid service port number. |
| 117 | You cannot change the UseConnection option while the component is active. |
| 135 | Operation would block. |
| 201 | Timeout. |
| 211 | Action impossible in control's present state. |
| 212 | Action impossible while not connected. |
| 213 | Action impossible while listening. |
| 301 | Timeout. |
| 303 | Could not open file. |
| 434 | Unable to convert string to selected CodePage. |
| 1105 | Already connecting. If you want to reconnect, close the current connection first. |
| 1117 | You need to connect first. |
| 1119 | You cannot change the LocalHost at this time. A connection is in progress. |
| 1120 | Connection dropped by remote host. |

### SSL Errors

|  |  |
| --- | --- |
| 270 | Cannot load specified security library. |
| 271 | Cannot open certificate store. |
| 272 | Cannot find specified certificate. |
| 273 | Cannot acquire security credentials. |
| 274 | Cannot find certificate chain. |
| 275 | Cannot verify certificate chain. |
| 276 | Error during handshake. |
| 280 | Error verifying certificate. |
| 281 | Could not find client certificate. |
| 282 | Could not find server certificate. |
| 283 | Error encrypting data. |
| 284 | Error decrypting data. |

### TCP/IP Errors

|  |  |
| --- | --- |
| 10004 | [10004] Interrupted system call. |
| 10009 | [10009] Bad file number. |
| 10013 | [10013] Access denied. |
| 10014 | [10014] Bad address. |
| 10022 | [10022] Invalid argument. |
| 10024 | [10024] Too many open files. |
| 10035 | [10035] Operation would block. |
| 10036 | [10036] Operation now in progress. |
| 10037 | [10037] Operation already in progress. |
| 10038 | [10038] Socket operation on nonsocket. |
| 10039 | [10039] Destination address required. |
| 10040 | [10040] Message is too long. |
| 10041 | [10041] Protocol wrong type for socket. |
| 10042 | [10042] Bad protocol option. |
| 10043 | [10043] Protocol is not supported. |
| 10044 | [10044] Socket type is not supported. |
| 10045 | [10045] Operation is not supported on socket. |
| 10046 | [10046] Protocol family is not supported. |
| 10047 | [10047] Address family is not supported by protocol family. |
| 10048 | [10048] Address already in use. |
| 10049 | [10049] Cannot assign requested address. |
| 10050 | [10050] Network is down. |
| 10051 | [10051] Network is unreachable. |
| 10052 | [10052] Net dropped connection or reset. |
| 10053 | [10053] Software caused connection abort. |
| 10054 | [10054] Connection reset by peer. |
| 10055 | [10055] No buffer space available. |
| 10056 | [10056] Socket is already connected. |
| 10057 | [10057] Socket is not connected. |
| 10058 | [10058] Cannot send after socket shutdown. |
| 10059 | [10059] Too many references, cannot splice. |
| 10060 | [10060] Connection timed out. |
| 10061 | [10061] Connection refused. |
| 10062 | [10062] Too many levels of symbolic links. |
| 10063 | [10063] File name is too long. |
| 10064 | [10064] Host is down. |
| 10065 | [10065] No route to host. |
| 10066 | [10066] Directory is not empty |
| 10067 | [10067] Too many processes. |
| 10068 | [10068] Too many users. |
| 10069 | [10069] Disc Quota Exceeded. |
| 10070 | [10070] Stale NFS file handle. |
| 10071 | [10071] Too many levels of remote in path. |
| 10091 | [10091] Network subsystem is unavailable. |
| 10092 | [10092] WINSOCK DLL Version out of range. |
| 10093 | [10093] Winsock is not loaded yet. |
| 11001 | [11001] Host not found. |
| 11002 | [11002] Nonauthoritative 'Host not found' (try again or check DNS setup). |
| 11003 | [11003] Nonrecoverable errors: FORMERR, REFUSED, NOTIMP. |
| 11004 | [11004] Valid name, no data record (check DNS setup). |