Finder which is used to look up the algorithm identifiers representing the encryption algorithms that
are associated with a particular signature algorithm.
Create a standard attribute table from the passed in parameters - this will
normally include contentType, signingTime, messageDigest, and CMS algorithm protection.
Generate a CMS Signed Data object which can be carrying a detached CMS signature, or have encapsulated data, depending on the value
of the encapsulated parameter.
the KeyTransRecipientInformation class for a recipient who has been sent a secret
key encrypted using their public key that needs to be used to
extract the message.
the KeyTransRecipientInformation class for a recipient who has been sent a secret
key encrypted using their public key that needs to be used to
extract the message.
the KeyTransRecipient class for a recipient who has been sent secret
key material encrypted using their public key that needs to be used to
derive a key and authenticate a message.
the KeyTransRecipient class for a recipient who has been sent secret
key material encrypted using their public key that needs to be used to
derive a key and extract a message.
the KeyTransRecipientInformation class for a recipient who has been sent a secret
key encrypted using their public key that needs to be used to
extract the message.
generate a signed object that for a CMS Signed Data
object using the given provider - if encapsulate is true a copy
of the message will be included in the signature.
generate a signed object that for a CMS Signed Data
object using the given provider - if encapsulate is true a copy
of the message will be included in the signature.
generate a signed object that for a CMS Signed Data
object using the given provider - if encapsulate is true a copy
of the message will be included in the signature with the
default content type "data".
generate a signed object that for a CMS Signed Data
object using the given provider - if encapsulate is true a copy
of the message will be included in the signature with the
default content type "data".
If the passed in flag is true, the signer signature will be based on the data, not
a collection of signed attributes, and no signed attributes will be included.
If the passed in flag is true, the signer signature will be based on the data, not
a collection of signed attributes, and no signed attributes will be included.
If the passed in flag is true, the signer signature will be based on the data, not
a collection of signed attributes, and no signed attributes will be included.
Representation of the authorization information (VO, server address
and list of Fully Qualified Attribute Names, or FQANs) contained in
a VOMS attribute certificate.