CMS Configuration
The component accepts one or more of the following configuration settings. Configuration settings are similar in functionality to properties, but they are rarely used. In order to avoid "polluting" the property namespace of the component, access to these internal properties is provided through the Config method.CMS Configuration Settings
| CompressBeforeSign: Specifies whether to compress before signing.When EnableCompression is set to True this property controls whether compression happens before or after signing. If set to True the input data will be compressed before signing. If set to False (default) the input data will be signed and then compressed. | |||||||||
| ContentTypeOID:
Specifies the oid for content type.This setting optionally specifies an OID defining the data content type for the data being processed. This may be set before calling Encrypt, Sign,
or SignAndEncrypt.
The default value is 1.2.840.113549.1.7.1 which is the OID for id-data. | |||||||||
| CSP:
The Cryptographic Service Provider.For the Win32 editions, the name of the Cryptographic Service Provider used to provide
access to encryption/decryption and signature operations.
NOTE: This config may only be used when the UseCryptoAPI is true. | |||||||||
| GenerateSignatureTimestamp:
Whether to generate timestamps in signatures.
If GenerateSignatureTimestamp is True, a timestamp will be generated and added to all signatures created by the component.
The default value is True. | |||||||||
| IncludeHeaders:
Tells the component whether to include the headers when encoding the message.If True (default), the component will include MIME headers when Sign, Encrypt,
or SignAndEncrypt are called. If False, only the message will be
encoded.
The default value for IncludeHeaders is true. Note: This setting is only applicable to when OutputFormat is set to SMIME. | |||||||||
| IncludeInternalHeaders:
Tells the component whether or not to include the internal headers when encoding the message.If True, the component will generate and include MIME part headers when
Sign, Encrypt, or SignAndEncrypt are called. When VerifySignature, Decrypt, or DecryptAndVerifySignature
are called the MIME part headers will be stripped.
When set to False, only the message will be processed, MIME part headers will not be generated or stripped. The default value for IncludeInternalHeaders is False. Note: This setting is only applicable to when OutputFormat is set to SMIME. | |||||||||
| InputContentTransferEncoding:
Sets the Content-Transfer-Encoding for the signed message.This setting specifies the Content-Transfer-Encoding header value in signed messages. By default the component
will automatically determine the Content-Transfer-Encoding based on the file extension set in InputFile, however
this setting may be set to override the determined value or to specify a value if data is read from InputMessage.
If no value is specified and a value cannot be automatically determined the default value 7bit will be used. Note: This setting is only applicable when OutputFormat is set to SMIME and when calling Sign or SignAndEncrypt and DetachedSignature is True. | |||||||||
| InputContentType:
Sets the Content-Type for the signed message.This setting specifies the Content-Type header value in signed messages. By default the component
will automatically determine the Content-Type based on the file extension set in InputFile, however
this setting may be set to override the determined value or to specify a value if data is read from InputMessage.
If no value is specified and a value cannot be automatically determined the default value text/plain; charset="iso-8859-1" will be used. Note: This setting is only applicable when OutputFormat is set to SMIME and when calling Sign or SignAndEncrypt and DetachedSignature is True. | |||||||||
| InputMessageHeaders: Message headers.This setting specifies the headers of the SMIME message if they are not already present in the input message. In most cases the input message itself will contain the necessary headers, however if the headers are and body of the SMIME message are separate, the headers may be specified in this setting before calling Decrypt, DecryptAndVerifySignature, or VerifySignature. | |||||||||
| LogDirectory: The directory on disk where debug logs are written.This setting specifies a directory on disk to which debug logs will be written during operation. This should only be set for debugging purposes. Files with various extensions will be written to disk at the location specified with debug data for the operation being performed. If LogFilename is not specified the filenames will be in the format yyyy-MM-dd-HH-mm-ss-fff. | |||||||||
| LogFilename: The base filename to use with LogDirectory.This setting specifies the base filename to use when LogDirectory is set. If specified the name should be a filename without extension. Various files will be logged with different extensions during operation. This setting defines only the base filename. If unspecified the files will be named with a timestamp in the format yyyy-MM-dd-HH-mm-ss-fff. | |||||||||
LogLevel:
The level of detail for log messages.This setting specifies the level of detail that is logged via the Log event. Possible values are:
| |||||||||
OAEPMGF1HashAlgorithm:
The MGF1 hash algorithm used with OAEP.This setting specifies the MGF1 hash algorithm used when UseOAEP is set to True. The default value is "SHA256". Possible
values are:
| |||||||||
| OAEPParams: The hex encoded OAEP parameters.This setting optionally specifies OAEP parameters to be used when UseOAEP is set to True. The specified value should be hex encoded. | |||||||||
OAEPRSAHashAlgorithm:
The RSA hash algorithm used with OAEP.This setting specifies thet RSA Hash Algorithm used when UseOAEP is set to True. The default value is "SHA256". Possible values are:
| |||||||||
| OutputMessageHeaders:
The SMIME headers of the output message.When IncludeHeaders is set to False the SMIME headers are not included in the output message itself
when Sign, Encrypt, or SignAndEncrypt are called.
This setting may be used to obtain the SMIME headers separately. This setting is only applicable when OutputFormat is set to SMIME.
| |||||||||
RecipientInfoType:
The type of signer information to include in the signed message.This setting specifies which type of information about the recipient's encryption certificate is included in the encrypted message. Possible values are:
Note: When subjectKeyIdentifier is selected the recipient's encryption certificate must contain the subjectKeyIdentifier extension. | |||||||||
| SignatureTimestamp: The signature timestamp in the signed message.This setting holds the timestamp of the signature. After calling VerifySignature this setting will hold the timestamp identifying when the signature was created. The timestamp is in UTC time with the format yyyyMMddHHmmss. For instance 20181130223821. | |||||||||
SignerInfoType:
The type of signer information to include in the signed message.This setting specifies which type of information about the signer certificate is included in the signed message. Possible values are:
Note: When subjectKeyIdentifier is selected the signing certificate must contain the subjectKeyIdentifier extension. | |||||||||
| UseAlgorithmOIDs:
Whether OIDs are used when providing information about the algorithms.This setting controls whether the EncryptionAlgorithm parameter of the RecipientInfo event
is populated with the name of the algorithm such as 3DES or the corresponding OID such as 1.2.840.113549.3.7.
The default value is False and the name of the algorithm is used. Set this to True to use the OIDs instead. |
Base Configuration Settings
| BuildInfo: Information about the product's build.When queried, this setting will return a string containing information about the product's build. | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| CodePage:
The system code page used for Unicode to Multibyte translations.The default code page is Unicode UTF-8 (65001).
The following is a list of valid code page identifiers:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
LicenseInfo:
Information about the current license.When queried, this setting will return a string containing information about the license this instance of a component is using. It will return the following information:
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| UseInternalSecurityAPI: Tells the component whether or not to use the system security libraries or an internal implementation. By default the component will use the system security libraries to perform cryptographic functions. Setting this to True tells the component to use the internal implementation instead of using the system's security API. |