GISBSender 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.GISBSender Configuration Settings
LogLevel: Specifies the level of detail that is logged.This setting is only applicable if PGPProviderType is set to Internal (1).
This setting controls the level of detail that is logged through the Status event. Possible values are:
| |||||||||||||||
| PGPCombineSignAndEncrypt: Whether to sign and encrypt in a single step or not.By default, when signing and encrypting the GISB data, the component will sign first and then
encrypt the signed message in a separate step. When this property is set to true, signing and
encrypting will be combined into a single step.
Note that if you are using an external provider (i.e. PGPProviderType is set to 0), setting PGPCombineSignAndEncrypt to true will cause the component to call the PGPProvider's SignAndEncrypt method. | |||||||||||||||
PGPProviderType: Which PGP implementation to use.This setting specifies which PGP provider is used. Possible values are:
By default the component will rely on an external provider such as GnuPG which is accessed through the interface dll specified by PGPProvider. When this property is set to 1 (Internal) all cryptographic operations will be performed by the component directly using an internal implementation. In this case PGPProvider is not used. When set to 1 (Internal) only the following parameters are applicable when calling SetPGPParam:
| |||||||||||||||
AuthScheme: The authorization scheme to be used when server authorization is to be performed.
Use the AuthScheme property to tell the component which type of authorization to perform when the User
and Password properties are set.
Possible values are:
For security reasons, setting this value will clear the values of User and Password. | |||||||||||||||
| Authorization: The Authorization string to be sent to the server.
If the Authorization setting contains a non-empty string,
an Authorization HTTP request header is added to the
request. This header conveys Authorization information to the
server.
This setting is provided so that the component can be extended with other security schemes in addition to the authorization schemes already implemented by the component. The AuthScheme; setting defines the authentication scheme used. In the case of HTTP Basic Authentication (default), every time User and Password are set, they are Base64 encoded, and the result is put in the Authorization setting in the form "Basic [encoded-user-password]". | |||||||||||||||
| User: A user name if authentication is to be used.If AuthScheme is set to Basic, the User and Password
are Base64 encoded and the result is put in the Authorization configuration setting
in the form "Basic [encoded-user-password]".
If AuthScheme is set to Digest, the User and Password properties are used to respond to the HTTP Digest Authentication challenge from the server. The User and Password properties must be set only after the URL property is set. When the URL property is set, for security reasons, User and Password are immediately cleared. | |||||||||||||||
| Password: A password if authentication is to be used.If AuthScheme is set to Basic, the User and Password are Base64 encoded and the result is put
in the Authorization configuration setting in the form "Basic [encoded-user-password]".
If AuthScheme is set to Digest, the User and Password properties are used to respond to the HTTP Digest Authentication challenge from the server. The User and Password properties must be set only after the URL property is set. When the URL property is set, for security reasons, User and Password are immediately cleared. | |||||||||||||||
| LogFilename: The base name of the log file.If set, this will be used as for the filename of the log file.
Note that only the base name should be specified as the component will append the appropriate file extension. |
Base Configuration Settings
| GUIAvailable: Tells the component whether or not a message loop is available for processing events.
In a GUI-based application, long-running blocking operations may cause the application to stop responding to input until the operation returns. The component will attempt to discover whether or not the application has a message loop and, if one is discovered, it will process events in that message loop during any such blocking operation.
In some non-GUI applications an invalid message loop may be discovered that will result in errant behavior. In these cases, setting GuiAvailable to false will ensure that the component does not attempt to process external events. | |
| UseBackgroundThread: Whether threads created by the component are background threads.If set to True, when the component creates a thread the thread's IsBackground property will be explicitly set to True. By default this setting is False. | |
| UseManagedSecurityAPI: Tells the component whether or not to use the system security libraries or a managed implementation.
By default the component will use the system security libraries to perform cryptographic functions. This means
calls to unmanaged code will be made. In certain environments this is not desirable. To use a completely managed security
implementation set this setting to True. Setting this to True tells the component to use the internal managed implementation
instead of using the system's security API.
Note that when this value is set the product's system dll is no longer required as a reference, as all unmanaged code is stored in this file. |