XmlDSig SQL Server Reference Documentation
XmlDSig
Current Version: 11.6.0
Chilkat.XmlDSig
Load an XML document containing one or more digital signatures and
inspect the signature structure before verification.
Work with documents that contain multiple signatures by selecting the
specific signature to inspect or verify.
Verify the cryptographic signature over the canonicalized
Check individual
Extract
Canonicalize XML for signature analysis and add an
For an extended overview, see
XmlDSig Class Overview.
Load, inspect, canonicalize, and verify XML Digital Signatures.
Chilkat.XmlDSig loads and verifies XML Digital Signatures. It
can inspect signed XML, select among multiple signatures in one document,
verify the overall SignatureValue, verify individual
Reference digests, handle external references, extract
KeyInfo, retrieve embedded certificates or public keys,
canonicalize XML, and add an EncapsulatedTimeStamp to an
existing signature.
Load signed XML
Select a signature
Verify SignatureValue
SignedInfo block.
Verify Reference digests
Reference digest values to confirm that
each signed item still matches what was originally signed.
Certificates and keys
KeyInfo, embedded signing certificates, or public
keys used to validate the signature.
Canonicalization and timestamps
EncapsulatedTimeStamp when timestamping an existing
signature.
SignatureValue, then verify the individual reference
digests. Use XmlDSig for verification and inspection; use
Chilkat.XmlDSigGen when creating new XML Digital Signatures.
Object Creation
DECLARE @hr int
DECLARE @xmlDSig int
EXEC @hr = sp_OACreate 'Chilkat.XmlDSig', @xmlDSig OUT
IF @hr <> 0
BEGIN
PRINT 'Failed to create ActiveX component'
RETURN
END
-- ... use @xmlDSig ...
EXEC @hr = sp_OADestroy @xmlDSigT-SQL uses the Chilkat ActiveX through the OLE Automation stored procedures. They must be enabled once on the server (EXEC sp_configure 'Ole Automation Procedures', 1; RECONFIGURE;), and the Chilkat ActiveX registered must match the bitness of the SQL Server instance (64-bit for a 64-bit SQL Server). To bind to a specific major version of Chilkat, append the major version number to the ProgID, such as sp_OACreate 'Chilkat.XmlDSig.11' for Chilkat v11.*.*.
sp_OACreate returns an object token (an int) that is passed as the first argument of every sp_OAMethod, sp_OAGetProperty and sp_OASetProperty call, and released with sp_OADestroy. Objects returned by methods (such as an HttpResponse or JsonObject) are also tokens received through an int OUT parameter; they must likewise be destroyed, and the OUT parameter is NULL when the method fails to return an object. Objects passed as arguments are passed by their token. When an OLE Automation procedure itself fails (non-zero @hr), sp_OAGetErrorInfo describes the error.
Data types: strings are nvarchar(4000); integers, booleans (1 or 0) and object tokens are int; dates are datetime. In the signatures on this page, @success, @iResult, @sResult and the like are the OUT variables receiving a method's return value, @iValue / @sValue receive or supply a property value, and the remaining @ variables are the method's arguments in order.
A string returned through an OUT parameter is limited to 4000 characters. For longer values, retrieve the result as a result set into a table variable instead of an OUT parameter, for example DECLARE @tmp TABLE (outputLine ntext) followed by INSERT INTO @tmp EXEC sp_OAGetProperty @xmlDSig, 'LastErrorText'. See string length limitations for strings returned by sp_OAMethod calls.
Methods that pass or return raw byte arrays are not shown on this page, because varbinary(max) values cannot be exchanged through sp_OAMethod (see varbinary(max) limitation). Use the BinData-based alternatives (methods ending in Bd) or the base64 / hex string-encoded variants instead. Binary properties (such as LastBinaryResult) can be retrieved as a result set into a table variable, as shown in their signatures. Asynchronous (*Async) methods and event callbacks are not available from SQL Server.
Properties
DebugLogFilePath
EXEC sp_OASetProperty @xmlDSig, 'DebugLogFilePath', @sValue
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.
ExternalRefDirs
EXEC sp_OASetProperty @xmlDSig, 'ExternalRefDirs', @sValue
May contain a set of directory paths specifying where referenced external files are located. Directory paths should be separated using a semicolon character. The default value of this property is the empty string which means no directories are automatically searched.
This property can be used if the external file referenced in the XML signature has the same filename as the file in the local filesystem.
IgnoreExternalRefs
EXEC sp_OASetProperty @xmlDSig, 'IgnoreExternalRefs', @iValue
If 1, then ignore failures caused by external references not being available. This allows for the XML signature to be at least partially validated if the external referenced files are not available. The default value of this property is 0.
LastBinaryResult
This property is mainly used in SQL Server stored procedures to retrieve binary data from the last method call that returned binary data. It is only accessible if Chilkat.Global.KeepBinaryResult is set to 1. This feature allows for the retrieval of large varbinary results in an SQL Server environment, which has restrictions on returning large data via method calls, though temp tables can handle binary properties.
LastErrorHtml
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
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
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
EXEC sp_OASetProperty @xmlDSig, 'LastMethodSuccess', @iValue
Indicates the success or failure of the most recent method call: 1 means success, 0 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.
LastStringResult
In SQL Server stored procedures, this property holds the string return value of the most recent method call that returns a string. It is accessible only when Chilkat.Global.KeepStringResult is set to TRUE. SQL Server has limitations on string lengths returned from methods and properties, but temp tables can be used to access large strings.
LastStringResultLen
The length, in characters, of the string contained in the LastStringResult property.
topNumReferences
The number of data objects referenced in the XML digital signature. A data object may be self-contained within the loaded XML signature, or it may be an external URI reference. An application can check each reference to see if it's external by calling IsReferenceExternal, and can get each reference URI by calling ReferenceUri.
NumSignatures
The number of digital signatures found within the loaded XML. Each digital signature is composed of XML having the following structure:
<Signature ID?>
<SignedInfo>
<CanonicalizationMethod/>
<SignatureMethod/>
(<Reference URI? >
(<Transforms>)?
<DigestMethod>
<DigestValue>
</Reference>)+
</SignedInfo>
<SignatureValue>
(<KeyInfo>)?
(<Object ID?>)*
</Signature>
Note: The Signature and other XML tags may be namespace prefixed.
The Selector property is used to select which XML signature is in effect when validating or calling other methods or properties.
RefFailReason
Indicates the failure reason for the last call to VerifyReferenceDigest. Possible values are:
- 0: No failure, the reference digest was valid.
- 1: The computed digest differs from the digest stored in the XML.
- 2: An external file is referenced, but it is unavailable for computing the digest.
- 3: The index argument passed to VerifyReferenceDigest was out of range.
- 4: Unable to find the Signature.
- 5: A transformation specified some sort of XML canonicalization that is not supported.
- 99: Unknown. (Should never get this value.)
Selector
EXEC sp_OASetProperty @xmlDSig, 'Selector', @iValue
If the loaded XML contains multiple signatures, this property can be set to specify which signature is in effect when calling other methods or properties. In most cases, the loaded XML contains a single signature and this property will remain at the default value of 0.
UncommonOptions
EXEC sp_OASetProperty @xmlDSig, 'UncommonOptions', @sValue
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
EXEC sp_OASetProperty @xmlDSig, 'VerboseLogging', @iValue
If set to 1, then the contents of LastErrorText (or LastErrorXml, or LastErrorHtml) may contain more verbose information. The default value is 0. Verbose logging should only be used for debugging. The potentially large quantity of logged information may adversely affect peformance.
Version
Methods
AddEncapsulatedTimeStamp
Adds an EncapsulatedTimeStamp to the signature indicated by the Selector property. The updated signed XML with the added EncapsulatedTimeStamp is returned in sbOut. See the example below for details.
Returns 1 for success, 0 for failure.
CanonicalizeFragment
Applies XML canonicalization to a fragment of the passed-in XML, and returns the canonicalized XML string. The fragmentId identifies the XML element where output begins. It is the XML element having an id attribute equal to fragmentId. The version may be one of the following:
C14N-- for Inclusive Canonical XMLEXCL_C14N-- for Exclusive Canonical XML
The prefixList only applies when the version is set to EXCL_C14N. The prefixList may be an empty string, or a SPACE separated list of namespace prefixes. It is the InclusiveNamespaces PrefixList, which is the list of namespaces that are propagated from ancestor elements for canonicalization purposes.
If withComments is 1, then XML comments are included in the output. If withComments is 0, then XML comments are excluded from the output.
Returns NULL on failure
CanonicalizeXml
Applies XML canonicalization to the passed-in XML, and returns the canonicalized XML string. The version may be one of the following:
C14N-- for Inclusive Canonical XMLEXCL_C14N-- for Exclusive Canonical XML
If withComments is 1, then XML comments are included in the output. If withComments is 0, then XML comments are excluded from the output.
Returns NULL on failure
GetCerts
Returns the certificates found in the signature indicated by the Selector property. The base64 representation of each certificate is returned.
Returns 1 for success, 0 for failure.
GetKeyInfo
Returns the KeyInfo XML for the signature indicated by the Selector property. Returns NULL if no KeyInfo exists.
Returns NULL on failure
GetPublicKey
Returns the public key from the KeyInfo XML for the signature indicated by the Selector property. Returns NULL if no KeyInfo exists, or if no public key is actually contained in the KeyInfo.
Returns NULL on failure
HasEncapsulatedTimeStamp
Returns 1 if the signature indicated by the Selector property contains an EncapsulatedTimeStamp. Otherwise returns 0.
IsReferenceExternal
Returns 1 if the reference at index is external. Each external reference would first need to be provided by the application prior to validating the signature.
LoadSignature
Loads an XML document containing 1 or more XML digital signatures. An application would first load XML containing digital signature(s), then validate. After loading, it is also possible to use various methods and properties to get information about the signature, such as the key info, references, etc. If external data is referenced by the signature, it may be necessary to provide the referenced data prior to validating.
Note: When loading an XML document, the Selector property is automatically reset to 0, and the NumSignatures property is set to the number of XML digital signatures found.
Returns 1 for success, 0 for failure.
topLoadSignatureBd
Loads an XML document containing one or more XML digital signatures from the contents of a BinData object. An application would first load the XML, then validate. After loading, it is also possible to use various methods and properties to get information about the signature, such as the key info, references, etc. If external data is referenced by the signature, it may be necessary to provide the referenced data prior to validating.
Note: When loading an XML document, the Selector property is automatically reset to 0, and the NumSignatures property is set to the number of XML digital signatures found.
Returns 1 for success, 0 for failure.
LoadSignatureSb
Loads an XML document containing one or more XML digital signatures from the contents of a StringBuilder object. An application would first load the XML, then validate. After loading, it is also possible to use various methods and properties to get information about the signature, such as the key info, references, etc. If external data is referenced by the signature, it may be necessary to provide the referenced data prior to validating.
Note: When loading an XML document, the Selector property is automatically reset to 0, and the NumSignatures property is set to the number of XML digital signatures found.
Returns 1 for success, 0 for failure.
ReferenceUri
Returns the URI of the Nth reference specified by index. (The 1st reference is at index 0.) URI's beginning with a pound sign ('#') are internal references.
Returns NULL on failure
SetHmacKey
Sets the HMAC key to be used if the Signature used 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 1 for success, 0 for 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.
SetPublicKey
Sets the public key to be used for verifying the signature indicated by the Selector property. A public key only needs to be explicitly provided by the application for those XML signatures where the public key is not already available within the KeyInfo of the Signature. In some cases, the KeyInfo within the Signature contains information about what public key was used for signing. The application can use this information to retrieve the matching public key and provide it via this method.
Returns 1 for success, 0 for failure.
SetRefDataBd
SetRefDataFile
Provides the data for the external reference at index. When validating the signature, the data contained in path will be streamed to compute the digest for validation.
SetRefDataSb
Provides the text data for the external reference at index. The charset specifies the byte representation of the text, such as utf-8, utf-16, windows-1252, etc. (If in doubt, try utf-8 first.)
UseCertVault
Adds an XML certificate vault to the object's internal list of sources to be searched for certificates having public keys when verifying an XML signature. A single XML certificate vault may be used. If UseCertVault is called multiple times, only the last certificate vault will be used, as each call to UseCertVault will replace the certificate vault provided in previous calls.
Returns 1 for success, 0 for failure.
VerifyReferenceDigest
This method allows for an application to verify the digest for each reference separately. This can be helpful if the full XMLDSIG validation fails, then one can test each referenced data's digest to see which, if any, fail to match.
VerifySignature
Verifies the signature indicated by the Selector property. If verifyReferenceDigests is 1, then the digest of each Reference within the signature's SignedInfo is also validated.
Returns 1 for success, 0 for failure.