- Encryption (for multiple recipients)
and decryption of strings and files are now supported. In order
to use the encryption features, a new license file is required.
- Additional certificate checking
parameters such as Certificate Policy, Certificate Chain and Certificate
Path Length have been added.
- SecureXML is now DoD JITC compliant.
Applications can now easily become DoD JITC compliant by setting
DoDCompliance property to 1. Please note that the end application
will still need to be tested by the JITC but its certification
is almost certain.
- Now CRL files and/or their URLs
can be provided externally if the certificates don’t contain
this information.
- Certficate trust can now be limited
to a set of selected root certificates.
SecureXML now outputs the
result of applying user contrained policies as well as authority
contrained policies.
- You can now provide a set of
detached object URIs when creating signature. SecureXML will add
additional references for these detached objects and include them
as part of the signature.
The following
object methods have been added:
- EncryptStr
- DecryptStr
- EncryptFile
- DecryptFile
- VerifyActiveCertificate
- ReadAllBase64
Following object
properties have been added:
- RecipientCertificates
- RecipientCertificateFiles
- RecipientCertificateStore
- DoDCompliance
- TrustedRoots
- CRLLocation
- CertificatePolicy
- AuthorityConstrainedPolicy
- UserConstrainedPolicy
- CertificatePolicyChecking
|
- CertificateChainValidation
- CertificatePathLengthChecking
- CertificatePolicyExplicit
- CertificateTrustExplicit
- DetachedObjects
- AttachedObjects
- DecryptionPFXCertFile
- DecryptUsingPFXFileCert
- DecryptionPFXPassword
- XpathNamespace
|
None
- URL reference is now allowed
for all signature modes (enveloped, enveloping and detached) of
the Sign method.
- The whole set of X509 certificates,
which make up the certificate chain are now included for each
signed document unless the ExcludeSignerCertificate property is
set to 1.
- SignDataStr now base64 encodes
the input string before creating the signature. A corresponding
base64 transform has been added hence the signed object is still
the original string. This is done to allow for non-XML characters
in the input string.
|
