XmlDSigGen Chilkat2 Java Reference Documentation

XmlDSigGen

Current Version: 11.7.0

Markdown version of this page for AI tools (v 11.7.0) · all AI docs

Chilkat.XmlDSigGen

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

Sign XML already present in the document, including enveloped signatures where the signature is inserted into the signed XML.

External references

Add references to external XML, text, binary data, files, or custom application-provided content.

Object and enveloping signatures

Build signatures that include signed data inside XML Object elements or produce enveloping signature structures.

Keys and KeyInfo

Sign with private keys or HMAC secrets and include certificate-based, public-key, or fully custom KeyInfo XML.

Canonicalization and transforms

Configure canonicalization, digest algorithms, signature algorithms, and reference transforms required by the receiving system.

Placement and compatibility

Control where the signature is inserted and enable compatibility behaviors for XML signature profiles with special formatting rules.

Common pattern: Configure the signature algorithm, canonicalization method, signing key or certificate, and 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

import com.chilkatsoft.chilkat2.ChilkatException;
import com.chilkatsoft.chilkat2.XmlDSigGen;

try (XmlDSigGen xmlDSigGen = new XmlDSigGen()) {
    // ... use xmlDSigGen ...
} catch (ChilkatException e) {
    System.out.println(e.getMessage());          // "XmlDSigGen.someMethod failed: <reason>"
    System.out.println(e.getLastErrorText());    // the full log of the failed call
}
public XmlDSigGen()

Creates the underlying native Chilkat object. The native library (chilkat2java) is loaded the first time any Chilkat2 object is created; see the README in the download for where it is looked for (-Dchilkat2.library.path, a classpath resource, or java.library.path).

public void close()

Releases the native object (XmlDSigGen is AutoCloseable, so try-with-resources calls it). Calling it again does nothing; any other method or property accessor called afterwards throws IllegalStateException. An object that is never closed is freed by a background cleaner once it becomes unreachable, but the garbage collector does not see native memory, so closing is the normal path. Objects returned by methods are owned by the caller too.

public boolean isClosed()

Returns true once close() has been called.

Errors

A method that fails throws ChilkatException, an unchecked exception carrying getClassName(), getMethodName(), getReason() (one line, also in the message) and getLastErrorText() (the full log, captured at the moment of the failure). The object remains usable. Methods that look something up and find nothing return null instead of throwing (each such method says so), and methods that answer a question (hasMember, isUnlocked, ...) return a plain boolean. Property accessors do not throw for Chilkat reasons.

A null string or object argument throws NullPointerException naming the parameter (except where a method documents that null is accepted), and a string containing U+0000 throws IllegalArgumentException.

Use an object from one thread at a time; it may be handed from one thread to another. The one cross-thread operation is setting setAbortCurrent(true) on an object that is busy in another thread (on the classes that have AbortCurrent). Unlocking: call new Global().unlockBundle("...") once at startup.

Properties

Behaviors
// read/write
String getBehaviors()
void setBehaviors(String value)
Introduced in version 9.5.0.70

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&#xD;
    BhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgG&#xD;
    A1UEChMRQ09NT0RPIENBIExpbWl0ZWQxPTA7BgNVBAMTNENPTU9ETyBSU0EgQ2xpZW50IEF1dGhl&#xD;
    ...
    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&#13;
    BhMCR0IxGzAZBgNVBAgTEkdyZWF0ZXIgTWFuY2hlc3RlcjEQMA4GA1UEBxMHU2FsZm9yZDEaMBgG&#13;
    A1UEChMRQ09NT0RPIENBIExpbWl0ZWQxPTA7BgNVBAMTNENPTU9ETyBSU0EgQ2xpZW50IEF1dGhl&#13;
    ...
    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 .nnn is 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:00 rather than Z to 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 as CN=..., O=..., OU=..., C=..., whereas normal order ends with CN, such as C=..., 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-60 will 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+60 will generate a signing time 60 seconds past the current time.
  • UBLDocumentSignatures Causes an XPath ancestor-or-self Transform 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.

top
CustomKeyInfoXml
// read/write
String getCustomKeyInfoXml()
void setCustomKeyInfoXml(String value)
Introduced in version 9.5.0.69

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.

top
DebugLogFilePath
// read/write
String getDebugLogFilePath()
void setDebugLogFilePath(String value)

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.

More Information and Examples
top
IncNamespacePrefix
// read/write
String getIncNamespacePrefix()
void setIncNamespacePrefix(String value)
Introduced in version 9.5.0.70

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
// read/write
String getIncNamespaceUri()
void setIncNamespaceUri(String value)
Introduced in version 9.5.0.70

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
// read/write
String getKeyInfoId()
void setKeyInfoId(String value)
Introduced in version 9.5.0.75

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
// read/write
String getKeyInfoKeyName()
void setKeyInfoKeyName(String value)
Introduced in version 9.5.0.69

Specifies the KeyName to be inserted in the KeyInfo element of the Signature if the KeyInfoType equals KeyName.

More Information and Examples
top
KeyInfoType
// read/write
String getKeyInfoType()
void setKeyInfoType(String value)
Introduced in version 9.5.0.69

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.

top
LastErrorHtml
// read-only
String getLastErrorHtml()

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.

top
LastErrorText
// read-only
String getLastErrorText()

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.

top
LastErrorXml
// read-only
String getLastErrorXml()

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.

top
LastMethodSuccess
// read/write
boolean getLastMethodSuccess()
void setLastMethodSuccess(boolean value)

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.

top
SigId
// read/write
String getSigId()
void setSigId(String value)
Introduced in version 9.5.0.69

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
// read/write
String getSigLocation()
void setSigLocation(String value)
Introduced in version 9.5.0.69

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>

top
SigLocationIdx
// read/write
int getSigLocationIdx()
void setSigLocationIdx(int value)
Introduced in version 11.1.0

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.)

top
SigLocationMod
// read/write
int getSigLocationMod()
void setSigLocationMod(int value)
Introduced in version 9.5.0.77

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.

top
SigNamespacePrefix
// read/write
String getSigNamespacePrefix()
void setSigNamespacePrefix(String value)
Introduced in version 9.5.0.69

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
// read/write
String getSigNamespaceUri()
void setSigNamespaceUri(String value)
Introduced in version 9.5.0.69

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
// read/write
String getSignedInfoCanonAlg()
void setSignedInfoCanonAlg(String value)
Introduced in version 9.5.0.69

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.

top
SignedInfoDigestMethod
// read/write
String getSignedInfoDigestMethod()
void setSignedInfoDigestMethod(String value)
Introduced in version 9.5.0.69

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.

top
SignedInfoId
// read/write
String getSignedInfoId()
void setSignedInfoId(String value)
Introduced in version 9.5.0.75

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.

top
SignedInfoPrefixList
// read/write
String getSignedInfoPrefixList()
void setSignedInfoPrefixList(String value)
Introduced in version 9.5.0.69

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>

top
SigningAlg
// read/write
String getSigningAlg()
void setSigningAlg(String value)
Introduced in version 9.5.0.69

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.

top
SigValueId
// read/write
String getSigValueId()
void setSigValueId(String value)
Introduced in version 9.5.0.75

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
// read/write
String getUncommonOptions()
void setUncommonOptions(String value)
Introduced in version 9.5.0.87

This is a catch-all property to be used for uncommon needs. This property defaults to the empty string, and should typically remain empty.

top
VerboseLogging
// read/write
boolean getVerboseLogging()
void setVerboseLogging(boolean value)

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.

top
Version
// read-only
String getVersion()

Version of the component/library, such as "10.1.0"

More Information and Examples
top
X509Type
// read/write
String getX509Type()
void setX509Type(String value)
Introduced in version 9.5.0.69

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.

top

Methods

AddEnvelopedRef
void addEnvelopedRef(String id, StringBuilder content, String digestMethod, String canonMethod, String refType)
Introduced in version 9.5.0.69

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.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
AddExternalBinaryRef
void addExternalBinaryRef(String uri, BinData content, String digestMethod, String refType)
Introduced in version 9.5.0.69

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.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
AddExternalFileRef
void addExternalFileRef(String uri, String localFilePath, String digestMethod, String refType)
Introduced in version 9.5.0.69

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.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
AddExternalTextRef
void addExternalTextRef(String uri, StringBuilder content, String charset, boolean includeBom, String digestMethod, String refType)
Introduced in version 9.5.0.69

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.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
AddExternalXmlRef
void addExternalXmlRef(String uri, StringBuilder content, String digestMethod, String canonMethod, String refType)
Introduced in version 9.5.0.69

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.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
AddObject
void addObject(String id, String content, String mimeType, String encoding)
Introduced in version 9.5.0.75

Specifies an Object to be added to the Signature.

  1. The id is the value of the Object element's Id attribute.
  2. The content contains the content of the Object element, which may be XML or plain text.
  3. The mimeType is the value of the Object element's MimeType attribute
  4. The encoding is the value of the Object element's Encoding attribute
In most cases, the mimeType and encoding are empty strings which cause the MimeType and Encoding attributes to be omitted.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
AddObjectRef
void addObjectRef(String id, String digestMethod, String canonMethod, String prefixList, String refType)
Introduced in version 9.5.0.75

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.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

More Information and Examples
top
AddObjectRef2
void addObjectRef2(String id, String digestMethod, Xml transforms, String refType)
Introduced in version 9.5.0.90

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.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
AddSameDocRef
void addSameDocRef(String id, String digestMethod, String canonMethod, String prefixList, String refType)
Introduced in version 9.5.0.69

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.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

More Information and Examples
top
AddSameDocRef2
void addSameDocRef2(String id, String digestMethod, Xml transforms, String refType)
Introduced in version 9.5.0.90

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.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
AddSignatureNamespace
void addSignatureNamespace(String nsPrefix, String nsUri)
Introduced in version 9.5.0.75

Can be called one or more times to add additional namespaces to the Signature element.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
ConstructSignedInfo
String constructSignedInfo(StringBuilder sbXml)
Introduced in version 9.5.0.74

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 ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
CreateXmlDSig
String createXmlDSig(String inXml)
Introduced in version 9.5.0.69

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 ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
CreateXmlDSigSb
void createXmlDSigSb(StringBuilder sbXml)
Introduced in version 9.5.0.69

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.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
SetHmacKey
void setHmacKey(String key, String encoding)
Introduced in version 9.5.0.69

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.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
SetHttpObj
void setHttpObj(Http http)
Introduced in version 9.5.0.90

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.

More Information and Examples
top
SetPrivateKey
void setPrivateKey(PrivateKey privKey)
Introduced in version 9.5.0.69

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.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
SetRefIdAttr
void setRefIdAttr(String uri_or_id, String value)
Introduced in version 9.5.0.75

Sets the Id attribute for a Reference.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

More Information and Examples
top
SetTsa
void setTsa(JsonObject json)
Introduced in version 9.5.0.90

Sets the TSA (Timestamp Authority) URL and other related settings for automatically adding an EncapsulatedTimestamp.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

top
SetX509Cert
void setX509Cert(Cert cert, boolean usePrivateKey)
Introduced in version 9.5.0.69

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.

Throws ChilkatException on failure; e.getLastErrorText() (or the object's getLastErrorText()) explains why, and the object remains usable.

More Information and Examples
top

Events

All Chilkat methods are synchronous: the call returns when the work is done. During a long-running call, XmlDSigGen reports progress through a ProgressListener, an interface with three methods, each with a default, so you override only what you need:

import com.chilkatsoft.chilkat2.ProgressListener;

xmlDSigGen.setProgressListener(new ProgressListener() {
    @Override public boolean percentDone(int pctDone) {
        System.out.println(pctDone + "%");
        return false;           // return true to abort the method in progress
    }
    @Override public void progressInfo(String name, String value) {
        System.out.println(name + ": " + value);
    }
});

For a single callback, a lambda is shorter:

xmlDSigGen.onPercentDone(pct -> { System.out.println(pct + "%"); return false; });
public void setProgressListener(ProgressListener listener)

Installs listener as the receiver of this object's events, replacing any listener or lambda installed before; null removes it.

public ProgressListener getProgressListener()

Returns the installed listener, or null.

public void onAbortCheck(BooleanSupplier callback)
public void onPercentDone(IntPredicate callback)
public void onProgressInfo(BiConsumer<String, String> callback)

Each installs a listener whose only callback is the given lambda (from java.util.function). Like setProgressListener, each replaces the listener installed before, so to handle more than one event, implement ProgressListener. null removes the listener.

abortCheck is called periodically during long operations; percentDone is called when an operation's completion percentage is known; progressInfo delivers named progress values. Returning true from abortCheck or percentDone aborts the running method, which then throws ChilkatException.

Callbacks run on the thread that called the method, before it returns. Inside a callback, property accessors of the object (such as setAbortCurrent(true)) and other objects may be used, but calling a method of the same object throws IllegalStateException. An exception thrown by a callback aborts the running method and is rethrown from it; the object remains usable.

AbortCheck
// ProgressListener method (default returns false), or onAbortCheck(BooleanSupplier)
boolean abortCheck()

Enables a method call to be aborted by triggering the AbortCheck event at intervals defined by the HeartbeatMs property. If HeartbeatMs is set to its default value of 0, no events will occur. For instance, set HeartbeatMs to 200 to trigger 5 AbortCheck events per second.

More Information and Examples

Example

import java.util.concurrent.atomic.AtomicBoolean;

final AtomicBoolean stop = new AtomicBoolean(false);   // another thread may call stop.set(true)
xmlDSigGen.onAbortCheck(() -> stop.get());
top
PercentDone
// ProgressListener method (default returns false), or onPercentDone(IntPredicate)
boolean percentDone(int pctDone)

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.

More Information and Examples

Example

xmlDSigGen.onPercentDone(pct -> {
    // pct ranges from 0 to 100.
    System.out.println("Percent done: " + pct);
    return false;   // return true to abort the method in progress
});
top
ProgressInfo
// ProgressListener method (default does nothing), or onProgressInfo(BiConsumer<String, String>)
void progressInfo(String name, String value)

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.

More Information and Examples

Example

xmlDSigGen.onProgressInfo((name, value) -> System.out.println(name + ": " + value));
top