XmlCertVault PureBasic Reference Documentation
XmlCertVault
Current Version: 11.5.0
Chilkat.XmlCertVault
Add certificates from
Import an entire
Load PEM files containing one or more certificates and/or private keys,
including encrypted PEM content when a password is supplied.
Add PFX data from a
Use
Export the vault with Collect certificates, certificate chains, PEM data, and PFX private keys in an XML vault.
Chilkat.XmlCertVault stores certificates and private-key
material in a portable XML-based certificate vault. It can add individual
certificates, certificate chains, DER or encoded certificates, PEM files,
certificate strings, and PFX/PKCS12 data from files, memory, encoded text, or
existing Chilkat objects. The vault can then be exported as XML, loaded from
XML, or saved to an XML file for later reuse by other Chilkat certificate and
TLS workflows.
Add certificates
Cert objects, files, PEM strings,
binary DER bytes, or encoded data such as Base64 or hex.
Add certificate chains
CertChain when related issuer and
intermediate certificates should be kept together in the vault.
Add PEM content
Add PFX / PKCS12
Pfx object, file, byte array, or encoded
string, using the PFX password to import private-key material.
Master password protection
MasterPassword to protect access to private keys stored
in the vault.
Load and save XML
GetXml, load it with
LoadXml or LoadXmlFile, and persist it with
SaveXml.
XmlCertVault, set MasterPassword when the
vault will contain private keys, add certificates or PFX/PEM material, then
save the vault with SaveXml or keep the XML string from
GetXml. Later, reload the same vault with LoadXml
or LoadXmlFile and provide the same master password before using
private keys.
MasterPassword, which is required to
access any private keys contained in the XML vault.
Object Creation
obj.i = CkXmlCertVault::ckCreate()
; Make sure to dispose of the object when finished like this:
CkXmlCertVault::ckDispose(obj);
Properties
DebugLogFilePath
Declare setCkDebugLogFilePath(obj.i, value.s)
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.
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
Declare setCkLastMethodSuccess(obj.i, value.i)
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.
MasterPassword
Declare setCkMasterPassword(obj.i, value.s)
The master password for the vault. Certificates are stored unencrypted, but private keys are stored 256-bit AES encrypted using the individual PFX passwords. The PFX passwords are stored 256-bit AES encrypted using the master password. The master password is required to acces any of the private keys stored within the XML vault.
topVerboseLogging
Declare setCkVerboseLogging(obj.i, value.i)
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
AddCert
AddCertChain
AddCertEncoded
Adds a certificate to the XML vault where certificate is passed directly from encoded bytes (such as Base64, Hex, etc.). The encoding is indicated by encoding.
Returns 1 for success, 0 for failure.
topAddCertFile
Adds a certificate to the XML vault.
Returns 1 for success, 0 for failure.
AddCertString
Adds a certificate from any string representation format such as PEM.
Returns 1 for success, 0 for failure.
AddPemFile
Adds the contents of a PEM file to the XML vault. The PEM file may be encrypted, and it may contain one or more certificates and/or private keys. The password is optional and only required if the PEM file contains encrypted content that requires a password.
Returns 1 for success, 0 for failure.
topAddPfx
AddPfxEncoded
Adds a PFX to the XML vault where PFX is passed directly from encoded bytes (such as Base64, Hex, etc.). The encoding is indicated by encoding.
Returns 1 for success, 0 for failure.
topAddPfxFile
GetXml
Returns the contents of the cert vault as an XML string.
Returns an empty string on failure. Use the LastMethodSuccess property to check for success.
top