#include <xmltooling/security/ChainingTrustEngine.h>
Inheritance diagram for xmltooling::ChainingTrustEngine:
Public Member Functions | |
ChainingTrustEngine (const xercesc::DOMElement *e=NULL) | |
Constructor. | |
virtual | ~ChainingTrustEngine () |
Destructor will delete any embedded engines. | |
void | addTrustEngine (TrustEngine *newEngine) |
Adds a trust engine for future calls. | |
TrustEngine * | removeTrustEngine (TrustEngine *oldEngine) |
Removes a trust engine. | |
bool | validate (xmlsignature::Signature &sig, const CredentialResolver &credResolver, CredentialCriteria *criteria=NULL) const |
Determines whether an XML signature is correct and valid with respect to the source of credentials supplied. | |
bool | validate (const XMLCh *sigAlgorithm, const char *sig, xmlsignature::KeyInfo *keyInfo, const char *in, unsigned int in_len, const CredentialResolver &credResolver, CredentialCriteria *criteria=NULL) const |
Determines whether a raw signature is correct and valid with respect to the source of credentials supplied. | |
bool | validate (XSECCryptoX509 *certEE, const std::vector< XSECCryptoX509 * > &certChain, const CredentialResolver &credResolver, CredentialCriteria *criteria=NULL) const |
Determines whether an X.509 credential is valid with respect to the source of credentials supplied. | |
bool | validate (X509 *certEE, STACK_OF(X509)*certChain, const CredentialResolver &credResolver, CredentialCriteria *criteria=NULL) const |
Determines whether an X.509 credential is valid with respect to the source of credentials supplied. |
|
Constructor. If a DOM is supplied, the following XML content is supported:
XML namespaces are ignored in the processing of this content.
|
|
Adds a trust engine for future calls.
|
|
Removes a trust engine. The caller must delete the engine if necessary.
|
|
Determines whether an X.509 credential is valid with respect to the source of credentials supplied. It is the responsibility of the application to ensure that the credentials supplied are in fact associated with the peer who presented the credential. If criteria with a peer name are supplied, the "name" of the EE certificate may also be checked to ensure that it identifies the intended peer. The peer name itself or implementation-specific rules based on the content of the peer credentials may be applied. Implementations may omit this check if they deem it unnecessary.
Implements xmltooling::OpenSSLTrustEngine. |
|
Determines whether an X.509 credential is valid with respect to the source of credentials supplied. It is the responsibility of the application to ensure that the credentials supplied are in fact associated with the peer who presented the credential. If criteria with a peer name are supplied, the "name" of the EE certificate may also be checked to ensure that it identifies the intended peer. The peer name itself or implementation-specific rules based on the content of the peer credentials may be applied. Implementations may omit this check if they deem it unnecessary.
Implements xmltooling::X509TrustEngine. |
|
Determines whether a raw signature is correct and valid with respect to the source of credentials supplied. It is the responsibility of the application to ensure that the Credentials supplied are in fact associated with the peer who created the signature. If criteria with a peer name are supplied, the "name" of the Credential that verifies the signature may also be checked to ensure that it identifies the intended peer. The peer name itself or implementation-specific rules based on the content of the peer credentials may be applied. Implementations may omit this check if they deem it unnecessary. Note that the keyInfo parameter is not part of the implicitly trusted set of information supplied via the CredentialResolver, but rather advisory data that may have accompanied the signature itself.
Implements xmltooling::SignatureTrustEngine. |
|
Determines whether an XML signature is correct and valid with respect to the source of credentials supplied. It is the responsibility of the application to ensure that the credentials supplied are in fact associated with the peer who created the signature. If criteria with a peer name are supplied, the "name" of the Credential that verifies the signature may also be checked to ensure that it identifies the intended peer. The peer name itself or implementation-specific rules based on the content of the peer credentials may be applied. Implementations may omit this check if they deem it unnecessary.
Implements xmltooling::SignatureTrustEngine. |