PDFVerify Component
Properties Methods Events Config Settings Errors
The PDFVerify component verifies PDF signatures.
Syntax
nsoftware.SecurePDF.PDFVerify
Remarks
The PDFVerify component verifies electronic signatures over PDF documents. Basic Adobe and PAdES signatures are supported.
PDFVerify validates each signature from two perspectives: the integrity and validity of the signature itself (i.e., its correspondence to the document data it covers), and the validity and trustworthiness of the signing certificate chain. These two signature aspects are generally independent of each other - the signature may be valid but the chain may not be trusted, or the chain may be trusted but the integrity of the signature may be violated. Under normal circumstances, both the signature and the chain must be valid for the signature to be considered good.
Preparing the Validation
To initiate the validation, first provide the signed PDF document as a file (InputFile), byte array (InputData), or stream (SetInputStream). Then adjust any chain validation parameters as necessary (please see the Chain Validation Setup section for more details) and call the Verify method.For every signature in the document, PDFVerify will fire the SignatureInfo event, allowing you to specify whether you want the component to validate the signature, the chain, or both.
Once SignatureInfo returns, PDFVerify proceeds to the signature validation routine in accordance with the provided settings.
Validation Results
Upon completion of the validation, the SignatureProcessed event is fired, and the validation results are published here as well as in the following fields of the associated PDFSignature object:
- SignatureValidationResult contains the outcome of the signature validation: valid, corrupted, the signing certificate was missing, or failed.
- ChainValidationResult contains the primary result of the chain validation routine: valid, valid but untrusted, invalid, or undefined.
- ChainValidationDetails provides the details of the factors that contributed to the chain validation result, such as an outdated certificate, a missing CRL, or a missing CA certificate.
Checking Signature Coverage
The PDF format uses incremental updates to introduce changes to the document. This implies that a signature may not cover the whole document, but rather a certain revision of it. Strictly speaking, every signature in a PDF document, apart from potentially the last one, covers just some part of the document. In most cases, that part matches the revision of the document that existed before all the subsequent signatures were added.Because of these specifics of the PDF format, it is crucially important to understand which part of the document is covered by a specific signature. Use the CoverageEndsAt field of the associated PDFSignature object to establish the scope of a signature. The revision of the document covered by that specific signature ranges from byte 0 to CoverageEndsAt. Alternatively, you can use the GetSignedVersion method to extract the signed revision to a file.
Chain Validation Setup
Chain validation is a sophisticated, multi-faceted 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 that these parameters apply to the Sign and Update methods in PDFSign as well as the Verify method in PDFVerify, as all three methods execute the chain validation procedure (if it is enabled).
Validation Policy
The ValidationPolicy property dictates how thoroughly the chain will be validated. It includes options to control which checks the component will perform, 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 property, which allows you to choose between and prioritize revocation origins. Note that 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 property, which allows you to specify the locations in which the component will search for trust anchors. Local system stores, your own trusted root certificates (via the TrustedCerts property), and Trusted Lists (via the TrustedLists property) are all supported.
Offline Mode
The OfflineMode property provides the ability to verify the document without contacting online sources. If this property is enabled, the component will only use KnownCerts, TrustedCerts, data structures within the document itself, 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 | A collection of all attached files found in the PDF document. |
BlockedCerts | The certificates that must be rejected as trust anchors. |
DecryptionCert | The decryption certificate. |
DocumentCerts | A collection of certificates read from the document during processing. |
Firewall | A set of properties related to firewall access. |
InputData | A byte array containing the PDF document to process. |
InputFile | The PDF file to process. |
KnownCerts | A collection of additional certificates for chain validation. |
OfflineMode | Whether the component is operating in offline mode. |
OutputData | A byte array containing the PDF document after processing. |
OutputFile | The path to a local file where the output will be written. |
Overwrite | Whether or not the component should overwrite files. |
Password | The password to decrypt the document with. |
Proxy | A set of properties related to proxy access. |
RevocationCheck | The kind(s) of revocation check to perform for all chain certificates. |
Signatures | A collection of all the signatures and empty fields found in the PDF document. |
TrustedCerts | A collection of trusted certificates for chain validation. |
TrustedLists | A list of known Trusted Lists for chain validation. |
TrustSources | The trust sources to use during chain validation. |
ValidationFlags | Additional chain validation settings. |
ValidationPolicy | The level at which to perform chain validation. |
ValidationTime | 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.
Close | Closes an opened PDF document. |
Config | Sets or retrieves a configuration setting. |
Encrypted | Checks whether a PDF document is encrypted. |
GetPageProperty | Retrieves the value of a page property. |
GetSignedVersion | Returns the part of a signed PDF document that is covered by the signature. |
Interrupt | Interrupts the current action. |
Open | Opens a PDF document for processing. |
Reset | Resets the component. |
SaveAttachment | Saves a PDF attachment to a file. |
SetInputStream | Sets the stream containing the PDF document to process. |
SetOutputStream | Sets the stream to write the processed document to. |
Signed | Checks whether a PDF document is signed. |
Unsign | Removes a signature from a PDF document. |
Verify | Verifies a signed PDF document. |
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 | Fired when the component encounters a chain certificate. |
DocumentInfo | Fired when the document has been loaded into memory. |
Error | Fired when information is available about errors during data delivery. |
Log | Fired once for each log message. |
Password | Fired when the component detects that the PDF document is encrypted with a password. |
RecipientInfo | Fired for each recipient certificate of the encrypted PDF document. |
SignatureInfo | Fired when the component finds a signature in the document. |
SignatureProcessed | Fired after a signature has been processed. |
SSLServerAuthentication | Fired after the server presents its certificate to the client. |
SSLStatus | 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.
CacheRevocationInfo | Whether to cache revocation information. |
CloseInputStreamAfterProcessing | Whether to close the input stream after processing. |
CloseOutputStreamAfterProcessing | Whether to close the output stream after processing. |
ContactInfo[Index] | The signer's contact information. |
FilterName[Index] | The signature filter name. |
FullSignatureName[Index] | The full name of the signature field. |
HTTPRetryCount | The number of HTTP request retries. |
HTTPRetryInterval | A time interval to apply between HTTP request retries. |
LogLevel | The level of detail that is logged. |
OwnerPassword | The owner password to decrypt the document with. |
Permissions | The document permissions associated with the encryption. |
PreferEmbeddedRevocationInfo | Whether to prioritize revocation information that is embedded into the document. |
SaveChanges | Whether to save changes made to the PDF document. |
SignatureData[Index] | The hex-encoded representation of the underlying PKCS#7 signature blob. |
TempPath | The location where temporary files are stored. |
BuildInfo | Information about the product's build. |
GUIAvailable | Whether or not a message loop is available for processing events. |
LicenseInfo | Information about the current license. |
MaskSensitiveData | Whether sensitive data is masked in log messages. |
UseInternalSecurityAPI | Whether or not to use the system security libraries or an internal implementation. |
Attachments Property (PDFVerify Component)
A collection of all attached files found in the PDF document.
Syntax
public PDFAttachmentList Attachments { get; }
Public Property Attachments As PDFAttachmentList
Remarks
This property is used to access the details of all the attached files identified in the document. Use the SaveAttachment method to save attachments from this collection.
This property is not available at design time.
Please refer to the PDFAttachment type for a complete list of fields.BlockedCerts Property (PDFVerify Component)
The certificates that must be rejected as trust anchors.
Syntax
public CertificateList BlockedCerts { get; }
Public Property BlockedCerts As CertificateList
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 type for a complete list of fields.DecryptionCert Property (PDFVerify Component)
The decryption certificate.
Syntax
public Certificate DecryptionCert { get; set; }
Public Property DecryptionCert As Certificate
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 type for a complete list of fields.DocumentCerts Property (PDFVerify Component)
A collection of certificates read from the document during processing.
Syntax
public CertificateList DocumentCerts { get; }
Public ReadOnly Property DocumentCerts As CertificateList
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 will be populated automatically during chain validation.
This property is read-only and not available at design time.
Please refer to the Certificate type for a complete list of fields.Firewall Property (PDFVerify Component)
A set of properties related to firewall access.
Syntax
Remarks
This is a Firewall-type property, which contains fields describing the firewall through which the component will attempt to connect.
Please refer to the Firewall type for a complete list of fields.InputData Property (PDFVerify Component)
A byte array containing the PDF document to process.
Syntax
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 (PDFVerify Component)
The PDF file to process.
Syntax
Default Value
""
Remarks
This property is used to provide a path to the PDF document to be processed.
KnownCerts Property (PDFVerify Component)
A collection of additional certificates for chain validation.
Syntax
public CertificateList KnownCerts { get; }
Public Property KnownCerts As CertificateList
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 instead.
This property is not available at design time.
Please refer to the Certificate type for a complete list of fields.OfflineMode Property (PDFVerify Component)
Whether the component is operating in offline mode.
Syntax
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.
OutputData Property (PDFVerify Component)
A byte array containing the PDF document after processing.
Syntax
Remarks
This property is used to read the byte array containing the produced output after the operation has completed. It will only be set if an output file and output stream have not been assigned via OutputFile and SetOutputStream respectively.
This property is read-only and not available at design time.
OutputFile Property (PDFVerify Component)
The path to a local file where the output will be written.
Syntax
Default Value
""
Remarks
This property is used to provide a path where the resulting PDF document will be saved after the operation has completed.
Overwrite Property (PDFVerify Component)
Whether or not the component should overwrite files.
Syntax
Default Value
False
Remarks
This property indicates whether or not the component will overwrite OutputFile, OutputData, or the stream set in SetOutputStream. If set to false, an error will be thrown whenever OutputFile, OutputData, or the stream set in SetOutputStream exists before an operation.
Password Property (PDFVerify Component)
The password to decrypt the document with.
Syntax
Default Value
""
Remarks
This property is used to provide the user password for decryption. Though it may be different from OwnerPassword, most implementations use the same value for both.
Proxy Property (PDFVerify Component)
A set of properties related to proxy access.
Syntax
Remarks
This property contains fields describing the proxy through which the component will attempt to connect.
Please refer to the Proxy type for a complete list of fields.RevocationCheck Property (PDFVerify Component)
The kind(s) of revocation check to perform for all chain certificates.
Syntax
public PDFVerifyRevocationChecks RevocationCheck { get; set; }
enum PDFVerifyRevocationChecks { rcAllCRL, rcAllOCSP, rcAllCRLAndOCSP, rcAnyCRL, rcAnyOCSP, rcAnyCRLOrOCSP, rcAnyOCSPOrCRL }
Public Property RevocationCheck As PdfverifyRevocationChecks
Enum PDFVerifyRevocationChecks rcAllCRL rcAllOCSP rcAllCRLAndOCSP rcAnyCRL rcAnyOCSP rcAnyCRLOrOCSP rcAnyOCSPOrCRL End Enum
Default Value
6
Remarks
This property is used to specify the revocation sources and preferences the component will use 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 will be checked, and all checks must succeed. |
1 (rcAllOCSP) | All provided OCSP endpoints will be checked, and all checks must succeed. |
2 (rcAllCRLAndOCSP) | All provided CRL and OCSP endpoints will be checked, and all checks must succeed. |
3 (rcAnyCRL) | All provided CRL endpoints will be checked, and at least one check must succeed. |
4 (rcAnyOCSP) | All provided OCSP endpoints will be checked, and at least one check must succeed. |
5 (rcAnyCRLOrOCSP) | All provided CRL and OCSP endpoints will be checked, and at least one check must succeed. CRL endpoints are checked first. |
6 (rcAnyOCSPOrCRL - default) | All provided CRL and OCSP endpoints will be 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 will be 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.
Signatures Property (PDFVerify Component)
A collection of all the signatures and empty fields found in the PDF document.
Syntax
public PDFSignatureList Signatures { get; }
Public ReadOnly Property Signatures As PDFSignatureList
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 type for a complete list of fields.TrustedCerts Property (PDFVerify Component)
A collection of trusted certificates for chain validation.
Syntax
public CertificateList TrustedCerts { get; }
Public Property TrustedCerts As CertificateList
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 forfeited 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 type for a complete list of fields.TrustedLists Property (PDFVerify Component)
A list of known Trusted Lists for chain validation.
Syntax
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 will consult 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. Custom values can be appended:
component.TrustedLists = "%EUTL%;http://my.company/tsl;c:\tsls\mytsl.xml";
Note: The component will cache 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 will retrieve the cached data and reuse them in the current
validation. If the data are invalid, the component will download a fresh Trusted List and add it to the cache.
TrustSources Property (PDFVerify Component)
The trust sources to use during chain validation.
Syntax
public PDFVerifyTrustSources TrustSources { get; set; }
enum PDFVerifyTrustSources { tsManual, tsLocal, tsTrustedLists, tsLocalAndTrustedLists }
Public Property TrustSources As PdfverifyTrustSources
Enum PDFVerifyTrustSources tsManual tsLocal tsTrustedLists tsLocalAndTrustedLists End Enum
Default Value
3
Remarks
This property is used to specify the sources the component will use 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 will consult the TrustedCerts property only. |
1 (tsLocal) | The component will consult local system stores (e.g., Windows Trusted Root Certification Authorities) as well as TrustedCerts. |
2 (tsTrustedLists) | The component will consult TrustedLists only. |
3 (tsLocalAndTrustedLists - default) | The component will consult local system stores, TrustedCerts, and TrustedLists. |
ValidationFlags Property (PDFVerify Component)
Additional chain validation settings.
Syntax
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 (PDFVerify Component)
The level at which to perform chain validation.
Syntax
public PDFVerifyValidationPolicies ValidationPolicy { get; set; }
enum PDFVerifyValidationPolicies { vpNone, vpFull, vpFullNoTrust, vpFullNoRevocation, vpBestEffort }
Public Property ValidationPolicy As PdfverifyValidationPolicies
Enum PDFVerifyValidationPolicies vpNone vpFull vpFullNoTrust vpFullNoRevocation vpBestEffort End Enum
Default Value
1
Remarks
This property is used to specify the overall validation policy the component will follow.
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 will depend 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 (PDFVerify Component)
The time point at which the signature should be validated.
Syntax
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 will then prioritize:
- The signature creation time if the signature contains a signature timestamp (ValidatedSigningTime), or
- The local time included in the signature by the signer (ClaimedSigningTime).
Close Method (PDFVerify Component)
Closes an opened PDF document.
Syntax
public void Close(); Async Version public async Task Close(); public async Task Close(CancellationToken cancellationToken);
Public Sub Close() Async Version Public Sub Close() As Task Public Sub Close(cancellationToken As CancellationToken) As Task
Remarks
This method is used to close the previously opened document specified in InputFile, InputData, or SetInputStream. It should always be preceded by a call to the Open method.
Example:
component.InputFile = "input.pdf";
component.Open();
// Some operation
component.Close();
If any changes are made to the document, they will be saved automatically to OutputFile, OutputData, or the stream set in SetOutputStream when this method is called. To configure this saving behavior, set the SaveChanges configuration setting.
Config Method (PDFVerify Component)
Sets or retrieves a configuration setting.
Syntax
Remarks
Config is a generic method available in every component. It is used to set and retrieve configuration settings 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, you must call Config("PROPERTY"). The value will be returned as a string.
Encrypted Method (PDFVerify Component)
Checks whether a PDF document is encrypted.
Syntax
public bool Encrypted(); Async Version public async Task<bool> Encrypted(); public async Task<bool> Encrypted(CancellationToken cancellationToken);
Public Function Encrypted() As Boolean Async Version Public Function Encrypted() As Task(Of Boolean) Public Function Encrypted(cancellationToken As CancellationToken) As Task(Of Boolean)
Remarks
This method is used to determine whether or not the document specified in InputFile, InputData, or SetInputStream is encrypted. It will return false if the document is pseudo-encrypted with an empty password.
Example:
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 will open it, perform the operation, then close it.
GetPageProperty Method (PDFVerify Component)
Retrieves the value of a page property.
Syntax
public string GetPageProperty(int page, string property); Async Version public async Task<string> GetPageProperty(int page, string property); public async Task<string> GetPageProperty(int page, string property, CancellationToken cancellationToken);
Public Function GetPageProperty(ByVal Page As Integer, ByVal Property As String) As String Async Version Public Function GetPageProperty(ByVal Page As Integer, ByVal Property As String) As Task(Of String) Public Function GetPageProperty(ByVal Page As Integer, ByVal Property As String, cancellationToken As CancellationToken) As Task(Of String)
Remarks
This method is used to read general information about the pages of the document specified in InputFile, InputData, or SetInputStream, such as their dimensions and content positioning details.
The Page parameter specifies the page to read information about, and the Property parameter specifies the page property to read. The latter can take one of the following values:
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. Both integer and decimal values are supported. |
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. Possible values: 0, 90, 180, 270. |
Width | 0 | The width of the page in points. Both integer and decimal values are supported. |
Note: Each page property is only populated once the document has been loaded, which is reported by the DocumentInfo event.
Example:
int pageCount = 0;
component.OnDocumentInfo += (s, e) => { pageCount = e.PageCount; };
component.InputFile = "input.pdf";
component.Open();
for (int i = 1; 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:
int x = int.Parse(pdfsign.GetPageProperty(1, "Width")) - 100;
int y = int.Parse(pdfsign.GetPageProperty(1, "Height")) - 100;
pdfsign.SetWidgetProperty("OffsetX", x.ToString());
pdfsign.SetWidgetProperty("OffsetY", y.ToString());
Note: If the document is not already opened, this method will open it, perform the operation, then close it.
GetSignedVersion Method (PDFVerify Component)
Returns the part of a signed PDF document that is covered by the signature.
Syntax
public void GetSignedVersion(int signatureIndex); Async Version public async Task GetSignedVersion(int signatureIndex); public async Task GetSignedVersion(int signatureIndex, CancellationToken cancellationToken);
Public Sub GetSignedVersion(ByVal SignatureIndex As Integer) Async Version Public Sub GetSignedVersion(ByVal SignatureIndex As Integer) As Task Public Sub GetSignedVersion(ByVal SignatureIndex As Integer, cancellationToken As CancellationToken) As Task
Remarks
This method is used to retrieve the revision of the document specified in InputFile, InputData, or SetInputStream that is covered by the signature specified by SignatureIndex. The extracted revision will be saved to OutputFile, OutputData, or the stream set in SetOutputStream.
The SignatureIndex parameter is the index of the signature of interest in the Signatures collection.
Example:
pdfverify.InputFile = "signed.pdf";
pdfverify.OutputFile = "revision0.pdf";
pdfverify.GetSignedVersion(0);
PDF documents often use an incremental update approach, with any changes being appended to the document without
altering the existing revision. This may lead to situations where a signature only covers part of the document
(one of the past revisions), but not subsequent changes. This method provides a means to extract the revision
that is actually certified by the signature.
It is recommended to use this method when validating signatures to make sure the signature covers the byte range it is expected to cover.
An alternative to this method is to check the CoverageEndsAt field of the signature object and match it to the document length.
Note: If the document is not already opened, this method will open it, perform the operation, then close it.
Interrupt Method (PDFVerify Component)
Interrupts the current action.
Syntax
public void Interrupt(); Async Version public async Task Interrupt(); public async Task Interrupt(CancellationToken cancellationToken);
Public Sub Interrupt() Async Version Public Sub Interrupt() As Task Public Sub Interrupt(cancellationToken As CancellationToken) As Task
Remarks
This method interrupts the current action. It can be used, for example, within the ChainCert event to abort the chain validation procedure.
If there is no action in progress, this method simply returns, doing nothing.
Open Method (PDFVerify Component)
Opens a PDF document for processing.
Syntax
public void Open(); Async Version public async Task Open(); public async Task Open(CancellationToken cancellationToken);
Public Sub Open() Async Version Public Sub Open() As Task Public Sub Open(cancellationToken As CancellationToken) As Task
Remarks
This method is used to open the document specified in InputFile, InputData, or SetInputStream before performing some operation on it, such as signing, updating, verifying signatures, or removing signatures. When finished, call Close to complete or discard the operation.
It is recommended to use this method (alongside Close) when performing multiple operations on the document at once.
Automatic Decryption Functionality
If this method is called on an encrypted document, the Password or RecipientInfo event will fire (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 will then attempt 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 the Decrypt method to save a decrypted copy of the document instead.
Reset Method (PDFVerify Component)
Resets the component.
Syntax
public void Reset(); Async Version public async Task Reset(); public async Task Reset(CancellationToken cancellationToken);
Public Sub Reset() Async Version Public Sub Reset() As Task Public Sub Reset(cancellationToken As CancellationToken) As Task
Remarks
This method is used to reset the component's properties and configuration settings to their default values.
SaveAttachment Method (PDFVerify Component)
Saves a PDF attachment to a file.
Syntax
Remarks
This method is used to retrieve the contents of an attachment from the document specified in InputFile, InputData, or SetInputStream and save it to the file specified by FileName. It does not modify the existence of the Attachments collection's contents.
The Index parameter is the index of the attachment in the Attachments collection to be saved.
The FileName parameter specifies the filename that the attachment will be saved to.
Example:
component.InputFile = "input_with_attachment.pdf";
component.Open();
component.SaveAttachment(0, "a.dat");
component.Close();
Example (saving to a stream):
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 will open it, perform the operation, then close it.
SetInputStream Method (PDFVerify Component)
Sets the stream containing the PDF document to process.
Syntax
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);
Public Sub SetInputStream(ByVal InputStream As System.IO.Stream) Async Version Public Sub SetInputStream(ByVal InputStream As System.IO.Stream) As Task Public Sub SetInputStream(ByVal InputStream As System.IO.Stream, cancellationToken As CancellationToken) As Task
Remarks
This method is used to set the stream from which the component will read the PDF document to be processed. If an input stream is set before the component attempts to perform operations on the document, the component will read the data from the input stream instead of from the InputFile or InputData properties.
Note: It may be useful to additionally set the CloseInputStreamAfterProcessing configuration setting to true when using input streams.
SetOutputStream Method (PDFVerify Component)
Sets the stream to write the processed document to.
Syntax
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);
Public Sub SetOutputStream(ByVal OutputStream As System.IO.Stream) Async Version Public Sub SetOutputStream(ByVal OutputStream As System.IO.Stream) As Task Public Sub SetOutputStream(ByVal OutputStream As System.IO.Stream, cancellationToken As CancellationToken) As Task
Remarks
This method is used to set the stream to which the component will write the resulting PDF document. If an output stream is set before the component attempts to perform operations on the document, the component will write the data to the output stream instead of writing to OutputFile or populating OutputData.
Note: It may be useful to additionally set the CloseOutputStreamAfterProcessing configuration setting to true when using output streams.
Signed Method (PDFVerify Component)
Checks whether a PDF document is signed.
Syntax
public bool Signed(); Async Version public async Task<bool> Signed(); public async Task<bool> Signed(CancellationToken cancellationToken);
Public Function Signed() As Boolean Async Version Public Function Signed() As Task(Of Boolean) Public Function Signed(cancellationToken As CancellationToken) As Task(Of Boolean)
Remarks
This method is used to determine whether or not the document specified in InputFile, InputData, or SetInputStream is signed. It will return false if the document contains only empty signature fields.
Example:
pdfverify.InputFile = "input.pdf";
if (pdfverify.Signed())
{
// Configure validation-related properties as desired
pdfverify.Verify();
}
Note: If the document is not already opened, this method will open it, perform the operation, then close it.
Unsign Method (PDFVerify Component)
Removes a signature from a PDF document.
Syntax
public void Unsign(int signatureIndex, int unsignKind); Async Version public async Task Unsign(int signatureIndex, int unsignKind); public async Task Unsign(int signatureIndex, int unsignKind, CancellationToken cancellationToken);
Public Sub Unsign(ByVal SignatureIndex As Integer, ByVal UnsignKind As Integer) Async Version Public Sub Unsign(ByVal SignatureIndex As Integer, ByVal UnsignKind As Integer) As Task Public Sub Unsign(ByVal SignatureIndex As Integer, ByVal UnsignKind As Integer, cancellationToken As CancellationToken) As Task
Remarks
This method is used to remove an existing signature specified by SignatureIndex from the document specified in InputFile, InputData, or SetInputStream. The document with the removed signature will be saved to OutputFile, OutputData, or the stream set in SetOutputStream.
The SignatureIndex parameter is the index of the signature in the Signatures collection to be removed.
The UnsignKind parameter specifies the kind of unsign to perform. Possible values are:
0 (uskFull) | Remove the signature fully. |
1 (uskKeepField) | Remove the signature, but keep the form field it is in. |
2 (uskKeepAppearance) | Remove the signature, but keep the form field and its widget. |
Example:
pdfverify.InputFile = "signed.pdf";
pdfverify.OutputFile = "unsigned.pdf";
pdfverify.Open();
int idx = pdfverify.Signatures.Count - 1;
pdfverify.Unsign(idx, 0); // uskFull
pdfverify.Close();
Note that unsigning is different from GetSignedVersion. The latter returns the revision of the document
including the mentioned signature (thus removing anything after that signature was created). Unsign
removes the signature completely by carving it out of the document.
Note: SignatureIndex set to -1 removes all signatures in the document.
Note: If the document is not already opened, this method will open it, perform the operation, then close it.
Verify Method (PDFVerify Component)
Verifies a signed PDF document.
Syntax
public void Verify(); Async Version public async Task Verify(); public async Task Verify(CancellationToken cancellationToken);
Public Sub Verify() Async Version Public Sub Verify() As Task Public Sub Verify(cancellationToken As CancellationToken) As Task
Remarks
This method is used to validate all signatures in the document specified in InputFile, InputData, or SetInputStream.
This method walks through the signed document and reports every signature via the SignatureInfo event. Subscribe to the event to be notified about the signatures and adjust validation settings on the fly.
Upon completion of this method, the signature details will be published in the Signatures property.
Example:
pdfverify.InputFile = "signed.pdf";
pdfverify.Verify();
PDFSignature signature = pdfverify.Signatures[0];
if (signature.SignatureValidationResult == SignatureValidationResults.svrValid)
Console.WriteLine("Signature is good");
if (signature.ChainValidationResult == ChainValidationResults.cvrValid)
Console.WriteLine("Chain is good");
This method only validates the signatures and does not check their coverage. It is a good idea to use mechanisms
such as GetSignedVersion or CoverageEndsAt to ensure that the
signature covers the expected document revision.
To control individual signature validation, subscribe to the SignatureInfo event and set the ValidateSignature and ValidateChain parameters accordingly. The results are reported via the SignatureProcessed event.
Use the following properties to adjust chain validation parameters:
- BlockedCerts
- KnownCerts
- OfflineMode
- RevocationCheck
- TrustedCerts
- TrustedLists
- TrustSources
- ValidationFlags
- ValidationPolicy
- ValidationTime
Note: If the document is not already opened, this method will open it, perform the operation, then close it.
ChainCert Event (PDFVerify Component)
Fired when the component encounters a chain certificate.
Syntax
public event OnChainCertHandler OnChainCert; public delegate void OnChainCertHandler(object sender, PDFVerifyChainCertEventArgs e); public class PDFVerifyChainCertEventArgs : 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; } }
Public Event OnChainCert As OnChainCertHandler Public Delegate Sub OnChainCertHandler(sender As Object, e As PDFVerifyChainCertEventArgs) Public Class PDFVerifyChainCertEventArgs Inherits EventArgs Public ReadOnly Property CertEncoded As String
Public ReadOnly Property CertEncodedB As Byte() Public ReadOnly Property CertSubject As String Public ReadOnly Property CertIssuer As String Public ReadOnly Property ValidationTime As String Public Property ValidationResult As Integer Public Property ValidationDetails As Integer End Class
Remarks
This event is fired once for each certificate encountered during chain validation to report that it is about to be processed. The component will try to retrieve all required chain certificates automatically.
The CertEncoded parameter specifies the PEM (Base64-encoded) public certificate.
The CertSubject and CertIssuer parameters specify the distinguished names of the certificate owner and issuer respectively.
The ValidationTime parameter specifies the time point (in UTC) at which the certificate validity was established.
The ValidationResult parameter 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, the ValidationDetails parameter 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 will follow 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)
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 (PDFVerify Component)
Fired when the document has been loaded into memory.
Syntax
public event OnDocumentInfoHandler OnDocumentInfo; public delegate void OnDocumentInfoHandler(object sender, PDFVerifyDocumentInfoEventArgs e); public class PDFVerifyDocumentInfoEventArgs : EventArgs { public int PageCount { get; } public int SignatureCount { get; } }
Public Event OnDocumentInfo As OnDocumentInfoHandler Public Delegate Sub OnDocumentInfoHandler(sender As Object, e As PDFVerifyDocumentInfoEventArgs) Public Class PDFVerifyDocumentInfoEventArgs Inherits EventArgs Public ReadOnly Property PageCount As Integer Public ReadOnly Property SignatureCount As Integer End Class
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, the GetPageProperty method can be used to find the optimal position for the signature widget.
The PageCount parameter reports the number of pages in the document.
The SignatureCount parameter reports the number of signatures in the document.
This event is fired when the Open method is called, but only after Password or RecipientInfo is fired (if applicable) and the document has been decrypted.
This event will populate the Attachments, DocumentCerts, and Signatures collections with any corresponding objects found in the document.
Error Event (PDFVerify Component)
Fired when information is available about errors during data delivery.
Syntax
public event OnErrorHandler OnError; public delegate void OnErrorHandler(object sender, PDFVerifyErrorEventArgs e); public class PDFVerifyErrorEventArgs : EventArgs { public int ErrorCode { get; } public string Description { get; } }
Public Event OnError As OnErrorHandler Public Delegate Sub OnErrorHandler(sender As Object, e As PDFVerifyErrorEventArgs) Public Class PDFVerifyErrorEventArgs Inherits EventArgs Public ReadOnly Property ErrorCode As Integer Public ReadOnly Property Description As String End Class
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 section.
Log Event (PDFVerify Component)
Fired once for each log message.
Syntax
public event OnLogHandler OnLog; public delegate void OnLogHandler(object sender, PDFVerifyLogEventArgs e); public class PDFVerifyLogEventArgs : EventArgs { public int LogLevel { get; } public string Message { get; } public string LogType { get; } }
Public Event OnLog As OnLogHandler Public Delegate Sub OnLogHandler(sender As Object, e As PDFVerifyLogEventArgs) Public Class PDFVerifyLogEventArgs Inherits EventArgs Public ReadOnly Property LogLevel As Integer Public ReadOnly Property Message As String Public ReadOnly Property LogType As String End Class
Remarks
This event is fired once for each log message generated by the component. The verbosity is controlled by the LogLevel configuration setting.
The LogLevel parameter 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. |
The Message parameter is the log message.
The LogType parameter identifies the type of log entry. Possible values are:
- CertValidator
- Font
- HTTP
- PDFInvalidSignature
- PDFRevocationInfo
- Timestamp
- TSL
Password Event (PDFVerify Component)
Fired when the component detects that the PDF document is encrypted with a password.
Syntax
public event OnPasswordHandler OnPassword; public delegate void OnPasswordHandler(object sender, PDFVerifyPasswordEventArgs e); public class PDFVerifyPasswordEventArgs : EventArgs { public bool Available { get; } public bool Cancel { get; set; } }
Public Event OnPassword As OnPasswordHandler Public Delegate Sub OnPasswordHandler(sender As Object, e As PDFVerifyPasswordEventArgs) Public Class PDFVerifyPasswordEventArgs Inherits EventArgs Public ReadOnly Property Available As Boolean Public Property Cancel As Boolean End Class
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 the Password property.
The Available parameter indicates whether the decryption password is already available to the component or still needs to be set. If this parameter is set to false, the correct password must be provided for the decryption attempt to succeed.
The Cancel parameter determines whether the component will stop firing this event to request a password.
RecipientInfo Event (PDFVerify Component)
Fired for each recipient certificate of the encrypted PDF document.
Syntax
public event OnRecipientInfoHandler OnRecipientInfo; public delegate void OnRecipientInfoHandler(object sender, PDFVerifyRecipientInfoEventArgs e); public class PDFVerifyRecipientInfoEventArgs : EventArgs { public string Issuer { get; } public string SerialNumber { get; } public string SubjectKeyIdentifier { get; } public bool Available { get; } public bool Cancel { get; set; } }
Public Event OnRecipientInfo As OnRecipientInfoHandler Public Delegate Sub OnRecipientInfoHandler(sender As Object, e As PDFVerifyRecipientInfoEventArgs) Public Class PDFVerifyRecipientInfoEventArgs Inherits EventArgs Public ReadOnly Property Issuer As String Public ReadOnly Property SerialNumber As String Public ReadOnly Property SubjectKeyIdentifier As String Public ReadOnly Property Available As Boolean Public Property Cancel As Boolean End Class
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 the DecryptionCert property.
The Issuer parameter specifies the subject of the issuer certificate.
The SerialNumber parameter specifies the serial number of the encryption certificate.
The SubjectKeyIdentifier parameter specifies the X.509 subjectKeyIdentifier extension value of the encryption certificate, encoded as a hex string.
The Available parameter indicates whether the decryption certificate is already available to the component or still needs to be set. If this parameter is set to false, the correct certificate must be provided for the decryption attempt to succeed.
The Cancel parameter 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 will cause its own invocation of this event.
SignatureInfo Event (PDFVerify Component)
Fired when the component finds a signature in the document.
Syntax
public event OnSignatureInfoHandler OnSignatureInfo; public delegate void OnSignatureInfoHandler(object sender, PDFVerifySignatureInfoEventArgs e); public class PDFVerifySignatureInfoEventArgs : EventArgs { public int SignatureIndex { get; } public bool ValidateSignature { get; set; } public bool ValidateChain { get; set; } }
Public Event OnSignatureInfo As OnSignatureInfoHandler Public Delegate Sub OnSignatureInfoHandler(sender As Object, e As PDFVerifySignatureInfoEventArgs) Public Class PDFVerifySignatureInfoEventArgs Inherits EventArgs Public ReadOnly Property SignatureIndex As Integer Public Property ValidateSignature As Boolean Public Property ValidateChain As Boolean End Class
Remarks
This event is fired once for each signature found in the document to report that the signature specified by SignatureIndex is about to be validated.
The SignatureIndex parameter is the index of the signature in the Signatures collection.
Signature validation consists of two independent stages: cryptographic signature validation and chain validation. The ValidateSignature and ValidateChain parameters 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). To skip validation entirely, set both parameters to false.
Use the following properties to adjust chain validation parameters:
- BlockedCerts
- KnownCerts
- OfflineMode
- RevocationCheck
- TrustedCerts
- TrustedLists
- TrustSources
- ValidationFlags
- ValidationPolicy
- ValidationTime
SignatureProcessed Event (PDFVerify Component)
Fired after a signature has been processed.
Syntax
public event OnSignatureProcessedHandler OnSignatureProcessed; public delegate void OnSignatureProcessedHandler(object sender, PDFVerifySignatureProcessedEventArgs e); public class PDFVerifySignatureProcessedEventArgs : EventArgs { public int SignatureIndex { get; } public int SignatureValidationResult { get; } public int ChainValidationResult { get; } public int ChainValidationDetails { get; } }
Public Event OnSignatureProcessed As OnSignatureProcessedHandler Public Delegate Sub OnSignatureProcessedHandler(sender As Object, e As PDFVerifySignatureProcessedEventArgs) Public Class PDFVerifySignatureProcessedEventArgs Inherits EventArgs Public ReadOnly Property SignatureIndex As Integer Public ReadOnly Property SignatureValidationResult As Integer Public ReadOnly Property ChainValidationResult As Integer Public ReadOnly Property ChainValidationDetails As Integer End Class
Remarks
This event is fired once for each signature found in the document to report that the signature specified by SignatureIndex has completed validation. It is fired after SignatureInfo if that event's ValidateSignature parameter is set to true.
The SignatureIndex parameter is the index of the signature in the Signatures collection.
Signature validation consists of two independent stages: cryptographic signature validation and chain validation. Separate validation results are reported for each in the SignatureValidationResult and ChainValidationResult parameters.
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, the ChainValidationDetails parameter 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 type.
SSLServerAuthentication Event (PDFVerify Component)
Fired after the server presents its certificate to the client.
Syntax
public event OnSSLServerAuthenticationHandler OnSSLServerAuthentication; public delegate void OnSSLServerAuthenticationHandler(object sender, PDFVerifySSLServerAuthenticationEventArgs e); public class PDFVerifySSLServerAuthenticationEventArgs : 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; } }
Public Event OnSSLServerAuthentication As OnSSLServerAuthenticationHandler Public Delegate Sub OnSSLServerAuthenticationHandler(sender As Object, e As PDFVerifySSLServerAuthenticationEventArgs) Public Class PDFVerifySSLServerAuthenticationEventArgs Inherits EventArgs Public ReadOnly Property CertEncoded As String
Public ReadOnly Property CertEncodedB As Byte() Public ReadOnly Property CertSubject As String Public ReadOnly Property CertIssuer As String Public ReadOnly Property Status As String Public Property Accept As Boolean End Class
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 or not to continue with the connection process. The Accept parameter 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 or not to continue.
When the Accept parameter is false, the Status parameter 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 the Accept parameter to true.
SSLStatus Event (PDFVerify Component)
Fired when secure connection progress messages are available.
Syntax
public event OnSSLStatusHandler OnSSLStatus; public delegate void OnSSLStatusHandler(object sender, PDFVerifySSLStatusEventArgs e); public class PDFVerifySSLStatusEventArgs : EventArgs { public string Message { get; } }
Public Event OnSSLStatus As OnSSLStatusHandler Public Delegate Sub OnSSLStatusHandler(sender As Object, e As PDFVerifySSLStatusEventArgs) Public Class PDFVerifySSLStatusEventArgs Inherits EventArgs Public ReadOnly Property Message As String End Class
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.
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 may be available but not exportable. In this case, PrivateKey returns an empty string.
PrivateKeyAvailable
bool (read-only)
Default: False
Whether a PrivateKey is available for the selected certificate. If 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 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 field denotes the type of the certificate store specified by Store. If the store is password-protected, specify the password in StorePassword.
Store is used in conjunction with the Subject field to specify client certificates. If Store has a value, and Subject or Encoded is set, a search for a certificate is initiated. Please see the 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 field denotes the type of the certificate store specified by Store. If the store is password-protected, specify the password in StorePassword.
Store is used in conjunction with the Subject field to specify client certificates. If Store has a value, and Subject or Encoded is set, a search for a certificate is initiated. Please see the 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:
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, the necessary data must first be collected using the CertMgr component. The ListStoreCertificates method may be called after setting CertStoreType to cstPKCS11, CertStorePassword to the PIN, and CertStore to the full path of the PKCS#11 DLL. The certificate information returned in the CertList event's CertEncoded parameter may be saved for later use. When using a certificate, pass the previously saved security key information as the Store and set StorePassword to the PIN. Code Example. SSH Authentication with Security Key:
|
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.
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 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 field for a text representation of 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=support@nsoftware.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 and Subject fields also may be used to specify a certificate.
When Encoded is set, a search is initiated in the current Store for the private key of the certificate. If the key is found, Subject is updated to reflect the full subject of the selected certificate; otherwise, 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 and Subject fields also may be used to specify a certificate.
When Encoded is set, a search is initiated in the current Store for the private key of the certificate. If the key is found, Subject is updated to reflect the full subject of the selected certificate; otherwise, Subject is set to an empty string.
Constructors
public Certificate();
Public Certificate()
Creates a instance whose properties can be set. This is useful for use with when generating new certificates.
public Certificate(string certificateFile);
Public Certificate(ByVal CertificateFile As String)
Opens CertificateFile and reads out the contents as an X.509 public key.
public Certificate(byte[] encoded);
Public Certificate(ByVal Encoded As Byte())
Parses Encoded as an X.509 public key.
public Certificate(CertStoreTypes storeType, string store, string storePassword, string subject);
Public Certificate(ByVal StoreType As CertStoreTypes, ByVal Store As String, ByVal StorePassword As String, ByVal Subject As String)
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.
public Certificate(CertStoreTypes storeType, string store, string storePassword, string subject, string configurationString);
Public Certificate(ByVal StoreType As CertStoreTypes, ByVal Store As String, ByVal StorePassword As String, ByVal Subject As String, ByVal ConfigurationString As String)
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.
public Certificate(CertStoreTypes storeType, string store, string storePassword, byte[] encoded);
Public Certificate(ByVal StoreType As CertStoreTypes, ByVal Store As String, ByVal StorePassword As String, ByVal Encoded As Byte())
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.
public Certificate(CertStoreTypes storeType, byte[] store, string storePassword, string subject);
Public Certificate(ByVal StoreType As CertStoreTypes, ByVal Store As Byte(), ByVal StorePassword As String, ByVal Subject As String)
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.
public Certificate(CertStoreTypes storeType, byte[] store, string storePassword, string subject, string configurationString);
Public Certificate(ByVal StoreType As CertStoreTypes, ByVal Store As Byte(), ByVal StorePassword As String, ByVal Subject As String, ByVal ConfigurationString As String)
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.
public Certificate(CertStoreTypes storeType, byte[] store, string storePassword, byte[] encoded);
Public Certificate(ByVal StoreType As CertStoreTypes, ByVal Store As Byte(), ByVal StorePassword As String, ByVal Encoded As Byte())
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 and the FirewallType.
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 is set to 80. |
fwSOCKS4 (2) | Connect through a SOCKS4 Proxy. Port is set to 1080. |
fwSOCKS5 (3) | Connect through a SOCKS5 Proxy. Port is set to 1080. |
fwSOCKS4A (10) | Connect through a SOCKS4A Proxy. Port is set to 1080. |
Host
string
Default: ""
The name or IP address of the firewall (optional). If a 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 is specified, the User and 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. See the description of the Host field for details.
Note: This field is set automatically when FirewallType is set to a valid value. See the description of the FirewallType field for details.
User
string
Default: ""
A username if authentication is to be used when connecting through a firewall. If Host is specified, this field and the Password field are used to connect and authenticate to the given Firewall. If the authentication fails, the component throws an exception.
Constructors
PDFAttachment Type
This describes the file being attached to the PDF document.
Remarks
This type contains information about the file that is being attached to the document.
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 is not set to a valid stream, the component will write to this field when an empty string is passed to the SaveAttachment method.
DataB
byte []
Default: ""
The raw data of the attachment.
If OutputStream is not set to a valid stream, the component will write to this field when an empty string is passed to the SaveAttachment method.
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 will attach 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 will write to this field when an empty string is passed to the SaveAttachment method.
Size
long (read-only)
Default: 0
The attachment's size in bytes.
Constructors
public PDFAttachment();
Public PDFAttachment()
public PDFAttachment(string fileName);
Public PDFAttachment(ByVal FileName As String)
public PDFAttachment(string fileName, string description);
Public PDFAttachment(ByVal FileName As String, ByVal Description As String)
public PDFAttachment(byte[] data, string name, string description);
Public PDFAttachment(ByVal Data As Byte(), ByVal Name As String, ByVal Description As String)
public PDFAttachment(System.IO.Stream inputStream, string name, string description);
Public PDFAttachment(ByVal InputStream As System.IO.Stream, ByVal Name As String, ByVal Description As String)
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.
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.
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 event to access the detailed validation log. This field is also available as a parameter of the SignatureProcessed 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 event to access the detailed validation log. This field is also available as a parameter of the SignatureProcessed 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, does not originate from a trusted TSA and may be forfeited or wrong.
CoverageEndsAt
int (read-only)
Default: 0
The 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 the GetSignedVersion method to extract the exact revision that was signed.
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 (set it to true to obtain the clean LTV capability) and CacheRevocationInfo (set it to false to prevent earlier validations from affecting the current validation).
Reason
string (read-only)
Default: ""
The reason for signing.
SignatureValidationResult
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 a parameter of the SignatureProcessed event.
SignerCertIndex
int (read-only)
Default: -1
The index of the signer certificate in the DocumentCerts collection.
TimestampCertIndex
int (read-only)
Default: -1
The index of the timestamping certificate in the DocumentCerts collection (if applicable).
Timestamped
bool (read-only)
Default: False
Whether the signature contains an embedded timestamp.
Type
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) |
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 nonempty if there is a valid timestamp included in the signature.
Note that the validated time, unlike ClaimedSigningTime, is the trusted signing time.
WidgetHeight
string (read-only)
Default: "70"
The height of the signature widget in points. Both integer and decimal values are supported.
WidgetOffsetX
string (read-only)
Default: "0"
The signature widget offset from the left-hand page border in points. Both integer and decimal values are supported.
WidgetOffsetY
string (read-only)
Default: "0"
The signature widget offset from the bottom page border in points. Both integer and decimal values are supported.
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. Both integer and decimal values are supported.
Constructors
public PDFSignature();
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 and the AuthScheme.
Fields
AuthScheme
ProxyAuthSchemes
Default: 0
The type of authorization to perform when connecting to the proxy. This is used only when the User and Password fields are set.
AuthScheme should be set to authNone (3) when no authentication is expected.
By default, AuthScheme is authBasic (0), and if the User and Password fields are set, the component will attempt basic authentication.
If AuthScheme is set to authDigest (1), digest authentication will be attempted instead.
If 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 is set to authNtlm (4), NTLM authentication will be used.
For security reasons, setting this field will clear the values of User and 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 is set to Basic Authentication, the User and Password fields are Base64 encoded and the proxy authentication token will be generated in the form Basic [encoded-user-password].
If AuthScheme is set to Digest Authentication, the User and Password fields are used to respond to the Digest Authentication challenge from the server.
If AuthScheme is set to NTLM Authentication, the User and Password fields are used to authenticate through NTLM negotiation.
Port
int
Default: 80
The Transmission Control Protocol (TCP) port for the proxy Server (default 80). See the description of the Server field for details.
Server
string
Default: ""
If a proxy Server is given, then the HTTP request is sent to the proxy instead of the server otherwise specified.
If the Server field is set to a domain name, a DNS request is initiated. Upon successful termination of the request, the 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 is set to Basic Authentication, the User and Password fields are Base64 encoded and the proxy authentication token will be generated in the form Basic [encoded-user-password].
If AuthScheme is set to Digest Authentication, the User and Password fields are used to respond to the Digest Authentication challenge from the server.
If AuthScheme is set to NTLM Authentication, the User and Password fields are used to authenticate through NTLM negotiation.
Constructors
Config Settings (PDFVerify 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 method.PDFVerify Config Settings
Index is the index of the signature in the Signatures collection. This setting is read-only.
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. |
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. |
0 | Discard all changes. |
1 | Save the document to OutputFile, OutputData, or the stream set in SetOutputStream, even if it has not been modified. |
2 (default) | Save the document to OutputFile, OutputData, or the stream set in SetOutputStream, but only if it has been modified. |
Base Config Settings
In some non-GUI applications, an invalid message loop may be discovered that will result in errant behavior. In these cases, setting GUIAvailable to false will ensure that the component does not attempt to process external events.
- 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.
This setting only works on these components: AS3Receiver, AS3Sender, Atom, Client(3DS), FTP, FTPServer, IMAP, OFTPClient, SSHClient, SCP, Server(3DS), Sexec, SFTP, SFTPServer, SSHServer, TCPClient, TCPServer.
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.
If using the .NET Standard Library, this setting will be true on all platforms. The .NET Standard library does not support using the system security libraries.
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 (PDFVerify Component)
PDFVerify Errors
802 | HTTP download failed. The error description contains the detailed message. |
803 | The document is not signed. |
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. |
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. |
844 | No signer certificate found. |
845 | Invalid signing certificate chain. The error description contains the detailed message. |
851 | Unsupported hash algorithm. |
853 | Invalid digest. |
854 | Invalid signature reference. |
855 | Invalid signature contents. |
856 | Invalid signature byte range. |
857 | Byte range does not cover the entire document. |
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 already exists and Overwrite 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 | No decryption key found. |
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. |
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. |
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 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). |