Uses of Class
br.ufsc.labsec.validationResult.results.reasons.ValidationResultReason
Packages that use ValidationResultReason
Package
Description
-
Uses of ValidationResultReason in br.ufsc.labsec.commons.report
Methods in br.ufsc.labsec.commons.report with parameters of type ValidationResultReasonModifier and TypeMethodDescriptionprotected voidReportWithValidation.buildReason(ValidationResultReason reason, ReportBuilder<?, ?> builder) -
Uses of ValidationResultReason in br.ufsc.labsec.validationResult.exceptions.indeterminateExceptions
Subclasses of ValidationResultReason in br.ufsc.labsec.validationResult.exceptions.indeterminateExceptionsModifier and TypeClassDescriptionclassclassAt least one of the algorithms that have been used in a material (e.g. the signature value, a certificate...) involved in validating the signature or the size of the keys used with such an algorithm is no longer considered reliable at the validation date/time.classAny other reason.classNo certificate chain has been found for the identified signer's certificate.classA proof of existence is missing to ascertain that a signed object has been produced before some compromising event (e.g. broken algorithm).classThe policy to use for validation could not be identifiedclassThe signer's certificate cannot be identifiedclassclassclassAt least one certificate chain was found but an intermediate CA certificate has been found to be revoked.classThe signer's certificate has been found to be revoked at the validation date/time.classCannot obtain signed data.classNot all constraints can be fulfilled using available information. -
Uses of ValidationResultReason in br.ufsc.labsec.validationResult.exceptions.invalidExceptions
Subclasses of ValidationResultReason in br.ufsc.labsec.validationResult.exceptions.invalidExceptionsModifier and TypeClassDescriptionclassThe signature is considered invalid because the certificate chain used in the validation process does not match the validation constraints related to the certificate.classThe signature is considered invalid because at least one of the algorithms that have been used in a material (e.g. the signature value, a certificate...) involved in validating the signature or the size of the keys used with such an algorithm is no longer considered reliable and the Signature Validation Algorithm can ascertain that this material was produced after the time up to which this algorithm was considered secure.classThe signature is considered invalid because the Signature Validation Algorithm can ascertain that the signing time lies after the expiration date (notAfter) of the signer's certificate.classThe signature has been found not conformant to one of the base standards (CAdES, XAdES, PAdES, JAdES).classThe signature is considered invalid because at least one hash of a signed data object(s) that has been included in the signing process does not match the corresponding hash value in the signature.classAny other reason.classThe signature is considered invalid because the Signature Validation Algorithm can ascertain that the signing time lies before the issuance date (notBefore) of the signer's certificate.classA given formal policy file could not be processed for any reason (e.g. not accessible, not parsable, etc.)classclassThe signature is considered invalid because: the signer's certificate has been found to be revoked; and the Signature Validation Algorithm can ascertain that the signing time lies after the revocation time. The validation process shall provide the following: the certificate chain used in the validation process; the time and the reason of revocation of the signer's certificate.classThe signature is considered invalid because one or more properties of the signature do not match the validation constraints.classThe signature is considered invalid because the signature value in the signature could not be verified using the signer's public key in the signer's certificate.classSome constraints on the order of signature time-stamps and/or signed data object (s) time-stamps are not respected.classThe signature was created using a policy and commitment type that is unknown to the SVA. -
Uses of ValidationResultReason in br.ufsc.labsec.validationResult.results
Fields in br.ufsc.labsec.validationResult.results with type parameters of type ValidationResultReasonModifier and TypeFieldDescriptionprotected List<ValidationResultReason> ValidationResult.validationResultReasonsRazões referentes ao resultado da validação.Methods in br.ufsc.labsec.validationResult.results that return types with arguments of type ValidationResultReasonModifier and TypeMethodDescriptionValidationResult.reasons()Retorna a razão para qual este resultado de validação encontra-se verdadeiro.Methods in br.ufsc.labsec.validationResult.results with parameters of type ValidationResultReasonModifier and TypeMethodDescriptionvoidValidationResult.addValidationResultReason(ValidationResultReason reason) Method parameters in br.ufsc.labsec.validationResult.results with type arguments of type ValidationResultReasonModifier and TypeMethodDescriptionbooleanValidationResult.removeIf(Predicate<ValidationResultReason> predicate) Constructor parameters in br.ufsc.labsec.validationResult.results with type arguments of type ValidationResultReasonModifierConstructorDescriptionValidationResult(List<ValidationResultReason> validationResultReasons) Construtor privado