XmlDSigGen React Native Reference Documentation
XmlDSigGen
Current Version: 11.6.1
Chilkat.XmlDSigGen
Sign XML already present in the document, including enveloped signatures
where the signature is inserted into the signed XML.
Add references to external XML, text, binary data, files, or custom
application-provided content.
Build signatures that include signed data inside XML
Sign with private keys or HMAC secrets and include certificate-based,
public-key, or fully custom
Configure canonicalization, digest algorithms, signature algorithms, and
reference transforms required by the receiving system.
Control where the signature is inserted and enable compatibility
behaviors for XML signature profiles with special formatting rules.
For an extended overview, see
XmlDSigGen Class Overview.
Create XML Digital Signatures with precise control over references, transforms, keys, and placement.
Chilkat.XmlDSigGen creates XML Digital Signatures for
same-document XML, external XML, text, binary, file, and
Object-based references. It supports enveloped, enveloping, and
detached-style signing workflows; X.509 certificate KeyInfo;
custom KeyInfo XML; RSA, DSA, and ECDSA private keys; HMAC
signatures; canonicalization options; reference transforms; signature
insertion placement; timestamp authority settings; and compatibility options
for systems with strict or unusual XML signature requirements.
Same-document signatures
External references
Object and enveloping signatures
Object elements or produce enveloping signature structures.
Keys and KeyInfo
KeyInfo XML.
Canonicalization and transforms
Placement and compatibility
KeyInfo style; add one or more references with
the required transforms and digest methods; choose where the signature should
be placed; then generate the signed XML. Use
Chilkat.XmlDSigGen to create signatures and
Chilkat.XmlDSig to inspect or verify them.
Object Creation
// npm install @chilkat/react-native react-native-nitro-modules
// (React Native 0.76+ with the New Architecture; then `pod install` for iOS. The Chilkat
// native library is downloaded and verified during the native build -- see the package README.)
import { Chilkat, XmlDSigGen } from '@chilkat/react-native'
// Once per app start, before any other Chilkat call:
Chilkat.unlockBundle('Anything for 30-day trial') // shorthand for new Global().unlockBundle(..)
const xmlDSigGen = new XmlDSigGen()
// ... the native object is released when `xmlDSigGen` is garbage collected, or now with xmlDSigGen.dispose()Creates the underlying native Chilkat object. XmlDSigGen is a Nitro Module HybridObject: use it from the JavaScript thread only (it cannot be passed to a Worklet or another runtime). Every member is synchronous and blocks the JavaScript thread until Chilkat returns; a method that can take a while also exists as a ...Async twin returning a Promise, which runs the same call on a native worker thread so the UI keeps rendering. While such a call is pending, every other call on this object throws, except abort() and assigning onPercentDone / onProgressInfo.
Releases the native object immediately instead of waiting for garbage collection (useful for a large BinData or an open socket). Calling it more than once is harmless; any other use of the object afterwards throws. An object with a pending ...Async call cannot be disposed until the promise settles.
Errors
A method that can fail throws a plain Error: a method whose only outcome is success or failure returns void and throws on failure; a method producing a string or an object returns it and throws where Chilkat would have returned null. The error's message is "Class.method(...): reason", where the reason is the last informative line of the object's lastErrorText, which holds the full Chilkat log of the failed call. A ...Async twin rejects its promise with the same Error instead of throwing. Properties never throw, and methods that answer a question (has..., is..., ...) return a plain boolean.
try {
xmlDSigGen.someMethod(...)
} catch (e) {
console.log((e as Error).message) // XmlDSigGen.someMethod(...): <reason>
console.log(xmlDSigGen.lastErrorText) // the full Chilkat log of the failed call
}
// The same call without blocking the JavaScript thread:
try {
await xmlDSigGen.someMethodAsync(...)
} catch (e) {
console.log((e as Error).message) // XmlDSigGen.someMethodAsync: <reason>
}
Properties
Behaviors
behaviors: string
A comma-separated list of keywords to specify special behaviors to work around potential oddities or special requirements needed for providing signatures to particular systems. This is an open-ended property where new behaviors can be implemented depending on the needs encountered by Chilkat customers. The possible behaviors are listed below.
- AttributeSortingBug (introduced in v9.5.0.79) Tells Chilkat to produce a signature that duplicates a common XML canonicalization attribute sorting bug found in some XML signature implementations (such as JPK VAT signed XML documents for Polish government, i.e. mf.gov.pl, csioz.gov.pl, crd.gov.pl, etc). See XML Signature Canonicalization Bug for details.
- Base64CrEntity Produce multi-line base64 for XML elements such as SignatureValue and X509Certificate, with each line ending in a CR hex entity, except for the last line. For example:
<ds:X509Certificate>MIIFNTCCBB2gAwIBAgIQHozVnBl1lTsusAh26u6WZTANBgkqhkiG9w0BAQsFADCBlzELMAkGA1UE
 BhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgG
 A1UEChMRQ09NT0RPIENBIExpbWl0ZWQxPTA7BgNVBAMTNENPTU9ETyBSU0EgQ2xpZW50IEF1dGhl
 ... sp3FRlACVeb1Qlytr4vgc5FlCqn0rMtjlF4= </ds:X509Certificate>
- Base64Cr13Entity Produce multi-line base64 for XML elements such as SignatureValue and X509Certificate, with each line ending in a CR decimal entity, except for the last line. For example:
<ds:X509Certificate>MIIFNTCCBB2gAwIBAgIQHozVnBl1lTsusAh26u6WZTANBgkqhkiG9w0BAQsFADCBlzELMAkGA1UE BhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgG A1UEChMRQ09NT0RPIENBIExpbWl0ZWQxPTA7BgNVBAMTNENPTU9ETyBSU0EgQ2xpZW50IEF1dGhl ... sp3FRlACVeb1Qlytr4vgc5FlCqn0rMtjlF4= </ds:X509Certificate>
- Base64Multiline Produce multi-line base64 for XML elements such as SignatureValue and X509Certificate. For example:
<ds:X509Certificate>MIIFNTCCBB2gAwIBAgIQHozVnBl1lTsusAh26u6WZTANBgkqhkiG9w0BAQsFADCBlzELMAkGA1UE BhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgG A1UEChMRQ09NT0RPIENBIExpbWl0ZWQxPTA7BgNVBAMTNENPTU9ETyBSU0EgQ2xpZW50IEF1dGhl ... sp3FRlACVeb1Qlytr4vgc5FlCqn0rMtjlF4= </ds:X509Certificate>
- ForceAddEnvelopedSignatureTransform The
<Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" />is normally only added when the Signature is contained within the XML fragment that is signed. The meaning of this tranformation is to tell the verifier to remove the Signature from the data prior to canonicalizing. If the Signature is not contained within the XML fragment that was signed, then the signature was not enveloped. There would be no need to remove the Signature because the Signature is not contained in the XML fragment being verified. However.. some brain-dead verifiying systems require this Transform to be present regardless of whether it makes sense. This behavior will cause Chilkat to add the Transform regardless. - NoEnvelopedSignatureTransform (introduced in v9.5.0.82) Prevents the
<Transform Algorithm="http://www.w3.org/2000/09/xmldsig#enveloped-signature" />from being added in all cases. - EnvelopedTransformFirst (introduced in v9.5.0.87) Forces the http://www.w3.org/2000/09/xmldsig#enveloped-signature to be listed first when there are multiple transforms for a reference.
- ebXmlTransform (introduced in v9.5.0.73) Causes the following tranform to be added for ebXml messages:
<Transform Algorithm=
http://www.w3.org/TR/1999/REC-xpath-19991116> <XPath xmlns:SOAP-ENV=http://schemas.xmlsoap.org/soap/envelope/>not(ancestor-or-self::node()[@SOAP-ENV:actor=urn:oasis:names:tc:ebxml-msg:actor:nextMSH] | ancestor-or-self::node()[@SOAP-ENV:actor=http://schemas.xmlsoap.org/soap/actor/next])</XPath> </Transform> - TransformSignatureXPath (introduced in v9.5.0.75) Causes the following tranform to be added:
<ds:Transform Algorithm=
http://www.w3.org/TR/1999/REC-xpath-19991116> <ds:XPath>not(ancestor-or-self::ds:Signature)</ds:XPath> </ds:Transform> - CompactSignedXml (introduced in v9.5.0.73) The passed-in XML to be signed is first reformatted to a compact representation by removing all CR's, LF's, and unnecessary whitespace so that the XML to be signed is on a single line. The resulting XML (with signature) is also entirely contained on a single line. (If an XML declarator is present, then it will remain on it's own line.)
- IndentedSignature (introduced in v9.5.0.73) Causes the XML Signature to be produced on multiple lines with indentation for easier human readability. The CompactSignedXml behavior takes precedence over this behavior.
- FullLocalSigningTime (introduced in v9.5.0.76) Causes the signing time to be formatted like this: 2017-05-20T19:16:05.649+01:00.nnn, where the
.nnnis added to indicate milliseconds. - LocalSigningTime (introduced in v9.5.0.76) Causes the signing time to be formatted using a local time (with a timezone offset such as
+01:00rather thanZto signify GMT). - NoReplaceSigningTime Don't replace the <SigningTime> content with a timestamp of the current date/time. Instead keep the current value provided by the application.
- NoTimestampBias Exclude the timestamp bias from the generated <SigningTime>
- DnReverseOrder (introduced in v9.5.0.77) Causes DN's (certificate Distinguished Names) to be written in reverse order. Reverse order leads with
CN, such asCN=..., O=..., OU=..., C=..., whereas normal order ends withCN, such asC=..., OU=..., O=..., CN=... - IssuerSerialHex (introduced in v9.5.0.77) Causes the issuer serial number located in SignedProperties.SignedSignatureProperties.SigningCertificate to be emitted as uppercase hex instead of decimal. (Also, when signing XML for e-dokumenty.mf.gov.pl, Chilkat automatically recognizes it and uses IssuerSerialHex.)
- IssuerSerialHexLower (introduced in v9.5.0.77) Causes the issuer serial number located in SignedProperties.SignedSignatureProperties.SigningCertificate to be emitted as lowercase hex instead of decimal.
- SigningTimeAdjust-<numSeconds> (introduced in v9.5.0.80) When Chilkat automatically fills in the value for a SigningTime, it will use the current system date/time. This behavior can be used to adjust the generate time to numSeconds in the past. For example:
SigningTimeAdjust-60will generate a signing time 60 seconds prior to the current time. - SigningTimeAdjust+<numSeconds> (introduced in v9.5.0.88) When Chilkat automatically fills in the value for a SigningTime, it will use the current system date/time. This behavior can be used to adjust the generate time to numSeconds in the future. For example:
SigningTimeAdjust+60will generate a signing time 60 seconds past the current time. - UBLDocumentSignatures Causes an XPath
ancestor-or-selfTransform to be added for the 1st reference. See the example at UBL XAdES Enveloped Signature - SignExistingSignatures This keyword can be used when applying a 2nd or greater signature and the new signature will encompass one or more existing signatures. The default behavior is that existing signatures are not included in the canonicalization/digest before signing. Adding this keyword will cause existing signatures to be included in the canonicalization/digest.
CustomKeyInfoXml
customKeyInfoXml: string
Specifies custom XML to be inserted in the KeyInfo element of the Signature. A common use is to provide a wsse:SecurityTokenReference fragment of XML.
DebugLogFilePath
debugLogFilePath: string
If set to a file path, this property logs the LastErrorText of each Chilkat method or property call to the specified file. This logging helps identify the context and history of Chilkat calls leading up to any crash or hang, aiding in debugging.
Enabling the VerboseLogging property provides more detailed information. This property is mainly used for debugging rare instances where a Chilkat method call causes a hang or crash, which should generally not happen.
Possible causes of hangs include:
- A timeout property set to 0, indicating an infinite timeout.
- A hang occurring within an event callback in the application code.
- An internal bug in the Chilkat code causing the hang.
IncNamespacePrefix
incNamespacePrefix: string
The namespace prefix to use for InclusiveNamespaces elements. The default value is ec. Set this property to the empty string to omit an InclusiveNamespaces prefix. For example, given the default values of IncNamespaceUri and IncNamespacePrefix, generated InclusiveNamespaces elements will appear like this:
<ec:InclusiveNamespaces xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#"> ... </ec:InclusiveNamespaces>top
IncNamespaceUri
incNamespaceUri: string
The namespace URI for any InclusiveNamespaces elements that are created. The default value is http://www.w3.org/2001/10/xml-exc-c14n#. For example, if the IncNamespacePrefix equals ec and this property remains at the default value, then the generated Signature element will be:
<ec:InclusiveNamespaces xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#"> ... </ec:InclusiveNamespaces>top
KeyInfoId
keyInfoId: string
If set, causes the generated KeyInfo element to include an Id attribute with this value. For example:
...
<ds:KeyInfo Id="KeyInfo">
<ds:X509Data>
<ds:X509SubjectName>CERTIFICADO DE ABC</ds:X509SubjectName>
<ds:X509Certificate>MIIITTCC....fIsIZeZOeQ=</ds:X509Certificate>
</ds:X509Data>
</ds:KeyInfo>
...
top
KeyInfoKeyName
keyInfoKeyName: string
Specifies the KeyName to be inserted in the KeyInfo element of the Signature if the KeyInfoType equals KeyName.
KeyInfoType
keyInfoType: string
Specifies the type of information that will be included in the optional KeyInfo element of the Signature. Possible values are:
- None
- KeyName
- KeyValue
- X509Data
- X509Data+KeyValue
- Custom
The default value is KeyValue. The X509Data+KeyValue option was added in Chilkat v9.5.0.73.
If None, then no KeyInfo element is added to the Signature when generated.
If KeyValue, then the KeyInfo will contain the public key (RSA, DSA, or ECDSA).
If X509Data, then the KeyInfo will contain information about an X.509 certificate as specified by the X509Type property.
If Custom, then the KeyInfo will contain the custom XML contained in the CustomKeyInfoXml property.
LastErrorHtml
readonly lastErrorHtml: string
Provides HTML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastErrorText
readonly lastErrorText: string
Provides plain text information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
LastErrorXml
readonly lastErrorXml: string
Provides XML-formatted information about the last called method or property. If a method call fails or behaves unexpectedly, check this property for details. Note that information is available regardless of the method call's success.
topLastMethodSuccess
lastMethodSuccess: boolean
Indicates the success or failure of the most recent method call: true means success, false means failure. This property remains unchanged by property setters or getters. This method is present to address challenges in checking for null or Nothing returns in certain programming languages. Note: This property does not apply to methods that return integer values or to boolean-returning methods where the boolean does not indicate success or failure.
SigId
sigId: string
An option Id attribute value for the Signature element. The default value is the empty string, which generates a Signature element with no Id attribute. For example:
<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#">If this property is set to "abc123", then the Signature element would be generated like this:
<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#" Id="abc123">top
SigLocation
sigLocation: string
Indicates where the Signature is to be located within the XML that is signed. This is a path to the position in the XML where the Signature will be inserted, using Chilkat path syntax (using vertical bar characters to delimit tag names. If the Signature element is to be the root of XML document, then set this property equal to the empty string.
For example, if we have the following SOAP XML and wish to insert the Signature at the indicated location, then the SigLocation property should be set to SOAP-ENV:Envelope|SOAP-ENV:Header|wsse:Security.
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header>
<wsse:Security xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurity-secext-1.0.xsd" SOAP-ENV:mustUnderstand="1">
** The XML Signature is to be inserted here **
</wsse:Security>
</SOAP-ENV:Header>
...
</SOAP-ENV:Envelope>
SigLocationIdx
sigLocationIdx: number
Insert the signature at the Nth occurrence of the SigLocation. The default is 0, which is to insert (according to SigLocationMod ) at the 1st occurrence. (An index value of 1 is for the 2nd occurrence, and so on.)
SigLocationMod
sigLocationMod: number
Modifies the placement of the signature at the location specified by SigLocation. Possible values are:
- 0: Insert the Signature as the last child of the element at SigLocation. This is the default.
- 1: Insert the Signature as a sibling directly after the element at SigLocation.
- 2: Insert the Signature as a sibling directly before the element at SigLocation.
SigNamespacePrefix
sigNamespacePrefix: string
The namespace prefix of the Signature that is to be created. The default value is ds. Set this property to the empty string to omit a Signature namespace URI and prefix. For example, given the default values of SigNamespaceUri and SigNamespacePrefix, the generated Signature element will be:
<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> ... </ds:Signature>top
SigNamespaceUri
sigNamespaceUri: string
The namespace URI of the Signature that is to be created. The default value is http://www.w3.org/2000/09/xmldsig#. For example, if the SigNamespacePrefix equals ds and this property remains at the default value, then the generated Signature element will be:
<ds:Signature xmlns:ds="http://www.w3.org/2000/09/xmldsig#"> ... </ds:Signature>top
SignedInfoCanonAlg
signedInfoCanonAlg: string
The canonicalization method to be used for the SignedInfo when creating the XML signature.
C14N-- for Inclusive Canonical XML (without comments)C14N_11-- for Inclusive Canonical XML 1.1 (without comments)EXCL_C14N-- for Exclusive Canonical XML (without comments)C14N_WithComments-- for Inclusive Canonical XML (with comments)C14N_11_WithComments-- for Inclusive Canonical XML 1.1 (with comments)EXCL_C14N_WithComments-- for Exclusive Canonical XML (with comments)- Note: The WithComments options are available in Chilkat v9.5.0.71 and later.
The default value is EXCL_C14N.
SignedInfoDigestMethod
signedInfoDigestMethod: string
The digest method to be used for signing the SignedInfo part of the Signature. Possible values are sha1, sha256, sha384, and sha512. The default is sha256.
SignedInfoId
signedInfoId: string
Optional Id attribute to be added to the SignedInfo element. The default value is the empty string, meaning that the SignedInfo is generated without an Id attribute.
topSignedInfoPrefixList
signedInfoPrefixList: string
The inclusive namespace prefix list to be added, if any, when the SignedInfoCanonAlg is equal to EXCL_C14N. The defautl value is the empty string. If namespaces are listed, they are separated by space characters.
If, for example, this property is set to wsse SOAP-ENV, then the CanonicalizationMethod part of the SignedInfo that is generated would look like this:
<ds:SignedInfo>
<ds:CanonicalizationMethod Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#">
<InclusiveNamespaces xmlns="http://www.w3.org/2001/10/xml-exc-c14n#" PrefixList="wsse SOAP-ENV" />
</ds:CanonicalizationMethod>
...
</ds:SignedInfo>
SigningAlg
signingAlg: string
Selects the signature algorithm to be used when using an RSA key to sign. The default value is PKCS1-v1_5. This can be set to RSASSA-PSS (or simply pss) to use the RSASSA-PSS signature scheme.
Note: This property only applies when signing with an RSA private key. It does not apply for ECC or DSA private keys.
topSigValueId
sigValueId: string
An option Id attribute value for the SignatureValue element. The default value is the empty string, which generates a SignatureValue element with no Id attribute. For example:
<ds:SignatureValue>If this property is set to "value-id-7d4a", then the Signature element would be generated like this:
<ds:SignatureValue Id="value-id-7d4a">top
UncommonOptions
uncommonOptions: string
This is a catch-all property to be used for uncommon needs. This property defaults to the empty string, and should typically remain empty.
topVerboseLogging
verboseLogging: boolean
If set to true, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is false. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.
Version
readonly version: string
X509Type
x509Type: string
Specifies the kind of X.509 certificate information is provided in the KeyInfo element when the KeyInfoType equals X509Data. Possible values are:
- Certificate
- CertChain
- IssuerSerial
- SubjectName
- SKI
The default value is Certificate.
Note: This property can be set to a comma-separated list of the keywords above. For example, If set to SubjectName,Certificate, then both the X509SubjectName and X509Certificate parts will be added to the KeyInfo.
If Certificate, then the KeyInfo will contain the base64 encoded X.509v3 certificate.
If CertChain, then the KeyInfo will contain the base64 encoded X.509v3 certificate as well as any certificates available in the chain of authentication to the root cert.
If IssuerSerial, then the KeyInfo will contain the X.509 issuer's distinguished name and the signing certificate's serial number.
If SubjectName, then the KeyInfo will contain the X.509 subject distinguished name.
If SKI, then the KeyInfo will contain the base64 encoded value of the cert's X.509 SubjectKeyIdentifier extension.
Methods
AddEnvelopedRef
Specifies an enveloped Reference to be added to the Signature when generated. An enveloped Reference is for data contained within the Signature. (The Signature is to be an enveloping signature, and the data is enveloped by the Signature.)
The id is the value of the Id attribute of the Object element that is to be contained within the generated Signature. The content is the text content to be contained in the Object. Binary data can be signed by passing the bytes in content in an encoded format (such as base64 or hex).
The digestMethod is the digest method and can be one of the following: sha1, sha256, sha384, sha512, ripemd160, or md5.
The canonMethod is the canonicalization method, and can be one of the following.
C14N-- for Inclusive Canonical XML (without comments)C14N_11-- for Inclusive Canonical XML 1.1 (without comments)EXCL_C14N-- for Exclusive Canonical XML (without comments)C14N_WithComments-- for Inclusive Canonical XML (with comments)C14N_11_WithComments-- for Inclusive Canonical XML 1.1 (with comments)EXCL_C14N_WithComments-- for Exclusive Canonical XML (with comments)- Note: The WithComments options are available in Chilkat v9.5.0.71 and later.
The refType is optional and is usually not needed. Set this to the empty string unless it is desired to add a Type attribute to the Reference that is advisory only.
Returns normally on success; throws an Error on failure.
AddExternalBinaryRef
Specifies an external non-XML binary data Reference to be added to the Signature when generated.
The uri is the value of the URI attribute of the Reference.
The content contains the binary data to be digested according to the digestMethod.
The digestMethod is the digest method and can be one of the following: sha1, sha256, sha384, sha512, ripemd160, or md5.
The refType is optional and is usually not needed. Set this to the empty string unless it is desired to add a Type attribute to the Reference that is advisory only.
Returns normally on success; throws an Error on failure.
AddExternalFileRef
Specifies an external file Reference to be added to the Signature when generated.
The uri is the value of the URI attribute of the Reference. It can (and likely will) be different than the localFilePath which is the path to the local file to be added. (The local file is not read until the XML digital signature is actually created.)
The digestMethod is the digest method and can be one of the following: sha1, sha256, sha384, sha512, ripemd160, or md5.
The refType is optional and is usually not needed. Set this to the empty string unless it is desired to add a Type attribute to the Reference that is advisory only.
Returns normally on success; throws an Error on failure.
AddExternalTextRef
Specifies an external non-XML text data Reference to be added to the Signature when generated.
The uri is the value of the URI attribute of the Reference.
The content contains the non-XML data to be digested according to the charset. The charset specifies the charset (such as utf-8, windows-1252, etc.) for the byte reprsentation of the text to be digested. The includeBom indicates whether the BOM (Byte Order Mark, also known as the preamble) is included in the byte representation that is digested.
The digestMethod is the digest method and can be one of the following: sha1, sha256, sha384, sha512, ripemd160, or md5.
The refType is optional and is usually not needed. Set this to the empty string unless it is desired to add a Type attribute to the Reference that is advisory only.
Returns normally on success; throws an Error on failure.
AddExternalXmlRef
Specifies an external XML Reference to be added to the Signature when generated.
The uri is the value of the URI attribute of the Reference.
The content contains the XML document to be referenced.
The digestMethod is the digest method and can be one of the following: sha1, sha256, sha384, sha512, ripemd160, or md5.
The canonMethod is the canonicalization method, and can be one of the following.
C14N-- for Inclusive Canonical XML (without comments)C14N_11-- for Inclusive Canonical XML 1.1 (without comments)EXCL_C14N-- for Exclusive Canonical XML (without comments)C14N_WithComments-- for Inclusive Canonical XML (with comments)C14N_11_WithComments-- for Inclusive Canonical XML 1.1 (with comments)EXCL_C14N_WithComments-- for Exclusive Canonical XML (with comments)-- An empty string indicates that no transformation should be included / applied for this reference.- Note: The WithComments options are available in Chilkat v9.5.0.71 and later.
- Note: The empty-string canonMethod is available in Chilkat v9.5.0.75 and later.
The refType is optional and is usually not needed. Set this to the empty string unless it is desired to add a Type attribute to the Reference that is advisory only.
Returns normally on success; throws an Error on failure.
AddObject
Specifies an Object to be added to the Signature.
- The
idis the value of the Object element's Id attribute. - The
contentcontains the content of the Object element, which may be XML or plain text. - The
mimeTypeis the value of the Object element's MimeType attribute - The
encodingis the value of the Object element's Encoding attribute
mimeType and encoding are empty strings which cause the MimeType and Encoding attributes to be omitted.Returns normally on success; throws an Error on failure.
AddObjectRef
This is the same as the AddSameDocRef method, except the reference is to content within an Object previously added via the AddObject method. The id must be an Id equal to the Id attribute of an Object, or the Id attribute of an element within the Object.
Note: The canonMethod can be set to Base64 to use the http://www.w3.org/2000/09/xmldsig#base64 transform.
Returns normally on success; throws an Error on failure.
AddObjectRef2
This method is the same as AddObjectRef, except it allows the Transforms to be specified exactly with a fragment of XML. See the example below.
Returns normally on success; throws an Error on failure.
AddSameDocRef
Specifies a same document Reference to be added to the Signature when generated. A same document Reference can be the entire XML document, or a fragment of the XML document.
The id can be the empty string to sign the entire XML document, or it can be the fragment identifier to sign a portion of the XML document.
The digestMethod is the digest method and can be one of the following: sha1, sha256, sha384, sha512, ripemd160, or md5.
The canonMethod is the canonicalization method, and can be one of the following:
C14N-- for Inclusive Canonical XML (without comments)C14N_11-- for Inclusive Canonical XML 1.1 (without comments)EXCL_C14N-- for Exclusive Canonical XML (without comments)C14N_WithComments-- for Inclusive Canonical XML (with comments)C14N_11_WithComments-- for Inclusive Canonical XML 1.1 (with comments)EXCL_C14N_WithComments-- for Exclusive Canonical XML (with comments)-- An empty string indicates that no transformation should be included / applied for this reference.- Note: The WithComments options are available in Chilkat v9.5.0.71 and later.
- Note: The empty-string canonMethod is available in Chilkat v9.5.0.75 and later.
If exclusive canonicalization is selected, then the prefixList can contain a space separated list of inclusive namespace prefixes. For inclusive canonicalization, this argument is ignored. In general, pass an empty string for this argument unless you have specific knowledge of namespace prefixes that need to be treated as inclusive when EXCL_C14N is used.
Starting in Chilkat v9.5.0.70, the prefixList can be set to the keyword _EMPTY_ to force the generation of an empty PrefixList under the Transform. For example:
<ds:Transform Algorithm="http://www.w3.org/2001/10/xml-exc-c14n#"> <ec:InclusiveNamespaces xmlns:ec="http://www.w3.org/2001/10/xml-exc-c14n#" PrefixList=""/> </ds:Transform>
The refType is optional and is usually not needed. Set this to the empty string unless it is desired to add a Type attribute to the Reference that is advisory only.
Returns normally on success; throws an Error on failure.
AddSameDocRef2
This method is the same as AddSameDocRef, except it allows the Transforms to be specified exactly with a fragment of XML. See the example below.
Returns normally on success; throws an Error on failure.
AddSignatureNamespace
Can be called one or more times to add additional namespaces to the Signature element.
Returns normally on success; throws an Error on failure.
ConstructSignedInfo
This method will construct and return the canonicalized SignedInfo XML. The digests of each Reference are computed and included in the SignedInfo. This method is provided for certain special circumstances where one wants to get the exact canonicalized SignedInfo that would be signed using the private key.
Note: Properties such as SigLocation, SigningAlg, etc. and references must be set exactly as if an XML signature was to be actually generated because they determine the content of the SignedInfo.
Note, the sbXml is not signed by this method. It is not modified.
Throws an Error on failure (where the description says null is returned, the method throws instead).
CreateXmlDSig
Creates an XML Digital Signature. The application passes in the XML to be signed, and the signed XML is returned. If creating an enveloping signature where the Signature element is the root, then the inXml may be the empty string.
- Chilkat v9.5.0.76 or greater is required for XML signatures for www.csioz.gov.pl
Throws an Error on failure (where the description says null is returned, the method throws instead).
CreateXmlDSigAsync
Asynchronous form of CreateXmlDSig: the same call on a native worker thread, so the JavaScript thread (and the UI) stays responsive. Takes the same arguments and resolves with the same result. While the returned Promise is pending, every other call on this object throws (the object is busy), except abort(), which cancels the call, and assigning the onPercentDone / onProgressInfo callbacks, which report its progress.
Note: the onPercentDone and onProgressInfo callbacks run on the JavaScript thread while the promise is pending, so they can update the UI directly. A rejection's message is "Class.methodAsync: reason"; the full log is in lastErrorText.
Returns a Promise that resolves with the synchronous method's result (undefined for a void method) and rejects with an Error where the synchronous method would throw.
CreateXmlDSigSb
Creates an XML Digital Signature. The application passes the XML to be signed in sbXml, and it is replaced with the signed XML if successful. (Thus, sbXml is both an input and output argument.) Note: If creating an enveloping signature where the Signature element is to be the root element, then the passed-in sbXml may be empty.
Returns normally on success; throws an Error on failure.
CreateXmlDSigSbAsync
Asynchronous form of CreateXmlDSigSb: the same call on a native worker thread, so the JavaScript thread (and the UI) stays responsive. Takes the same arguments and resolves with the same result. While the returned Promise is pending, every other call on this object throws (the object is busy), except abort(), which cancels the call, and assigning the onPercentDone / onProgressInfo callbacks, which report its progress.
Note: the onPercentDone and onProgressInfo callbacks run on the JavaScript thread while the promise is pending, so they can update the UI directly. A rejection's message is "Class.methodAsync: reason"; the full log is in lastErrorText.
Returns a Promise that resolves with the synchronous method's result (undefined for a void method) and rejects with an Error where the synchronous method would throw.
SetHmacKey
Sets the HMAC key to be used if the Signature is to use an HMAC signing algorithm. The encoding specifies the encoding of key, and can be hex, base64, ascii, or any of the binary encodings supported by Chilkat in the link below.
Returns normally on success; throws an Error on failure.
SetHttpObj
Sets the HTTP object to be used to communicate with OCSP responders, CRL distribution points, or timestamp authority (TSA) servers if needed. The http is used to send the requests, and it allows for connection related settings and timeouts to be set. For example, if HTTP or SOCKS proxies are required, these features can be specified on the http.
SetPrivateKey
Sets the private key to be used for creating the XML signature. The private key may be an RSA key, a DSA key, or an ECDSA key.
Returns normally on success; throws an Error on failure.
SetRefIdAttr
Sets the Id attribute for a Reference.
Returns normally on success; throws an Error on failure.
SetTsa
Sets the TSA (Timestamp Authority) URL and other related settings for automatically adding an EncapsulatedTimestamp.
Returns normally on success; throws an Error on failure.
SetX509Cert
Specifies the X.509 certificate to be used for the KeyInfo element when the KeyInfoType equals X509Data. If usePrivateKey is true, then the private key will also be set using the certificate's private key. Thus, the SetPrivateKey method does not need to be called. If usePrivateKey is true, and the certificate does not have an associated private key available, then this method will return false.
Note: A certificate's private key is not stored within a certificate itself. If the certificate (cert) was obtained from a PFX, Java KeyStore, or other such source, which are containers for both certs and private keys, then Chilkat would have associated the cert with the private key when loading the PFX or JKS, and all is good. The same holds true if, on a Windows system, the certificate was obtained from a Windows-based registry certificate store where the private key was installed with the permission to export.
If, however, the certificate was loaded from a .cer file, or another type of file that contains only the certificate and not the private key, then the associated private key needs to be obtained by the application and provided by calling SetPrivateKey.
Returns normally on success; throws an Error on failure.
Events
While a method runs, XmlDSigGen reports progress through two optional callback properties. Assign a function to receive the event, or undefined to stop receiving it. The callbacks are delivered on the JavaScript thread, so they are useful with the ...Async methods: during a synchronous call the JavaScript thread is busy inside Chilkat, and the events can only arrive after it returns.
const xmlDSigGen = new XmlDSigGen()
xmlDSigGen.onPercentDone = (pct) => setProgress(pct) // pct is 0..100
xmlDSigGen.onProgressInfo = (name, value) => console.log(`${name}: ${value}`)
xmlDSigGen.heartbeatMs = 250 // let abort() take effect within a quarter second
const pending = xmlDSigGen.someMethodAsync(...)
cancelButton.onPress = () => xmlDSigGen.abort() // the promise then rejects
await pendingPercentDone fires when an operation's completion percentage is known; ProgressInfo delivers named progress values (what is reported depends on the class and method). There is no AbortCheck callback: to cancel a pending ...Async call, call abort() on the object. Chilkat notices the request at its next progress check, which happens at least every heartbeatMs milliseconds on the classes that have that property (0, the default, disables the heartbeat, so set it for a responsive cancel), and the promise rejects with Chilkat's abort error. abort() is harmless when nothing is pending.
PercentDone
onPercentDone?: (pctDone: number) => void
This provides the percentage completion for any method involving network communications or time-consuming processing, assuming the progress can be measured as a percentage. This event is triggered only when it's possible and logical to express the operation's progress as a percentage. The pctDone argument will range from 1 to 100. For methods that finish quickly, the number of PercentDone callbacks may vary, but the final callback will have pctDone equal to 100. For longer operations, callbacks will not exceed one per percentage point (e.g., 1, 2, 3, ..., 98, 99, 100).
The PercentDone callback also acts as an AbortCheck event. For fast methods where PercentDone fires, an AbortCheck event may not trigger since the PercentDone callback already provides an opportunity to abort. For longer operations, where time between PercentDone callbacks is extended, AbortCheck callbacks enable more responsive operation termination.
To abort the operation, set the abort output argument to true. This will cause the method to terminate and return a failure status or corresponding failure value.
Example:
xmlDSigGen.onPercentDone = (pct) => {
// pct ranges from 0 to 100.
setProgress(pct) // runs on the JavaScript thread: React state may be updated directly
}
await xmlDSigGen.someMethodAsync(...)
// To stop an operation from within the callback, call xmlDSigGen.abort()ProgressInfo
onProgressInfo?: (name: string, value: string) => void
This event callback provides tag name/value pairs that detail what occurs during a method call. To discover existing tag names, create code to handle the event, emit the pairs, and review them. Most tag names are self-explanatory.
Note: Some Chilkat methods don't fire any ProgressInfo events.
Example:
xmlDSigGen.onProgressInfo = (name, value) => console.log(`${name}: ${value}`)
await xmlDSigGen.someMethodAsync(...)