05/12/2017
Dears,
There was an error occurred when verifying "security certificate validation"
007.js and 008.js title shows we should get a response with status BadSecurtiyChecksFailed if client side use Expired / Not-yet-valid certificate.
But the error shows the expected result is Good or BadCertificateTimeInvalid.
It made me confused.
Could you tell me how to handle this part?
CTT tool version: 1.2.336.273
Moderators-Specifications
Moderators-Companion
Moderators-Implementation
Moderators-Certification
Moderators-COM
02/24/2014
The test cases are correct as it is written. In an earlier version of the specification when the test cases where initially generate all security checks were expected to return BadSecurityChecksFailed, but this was corrected for a few test cases where the certificate and communication has been validated but a minor error has occurred. The additional information that the certificate has expired is allowed to be returned. In addition the specification allows a server to be configured to ignore that a certificate is expired error and continue to use the certificate (good result). The server is required to log or otherwise report (internally) that the certificate is expired in the case of a good result.
In a future version of the CTT we will rename the test case and remove the "Expects BadSecurityCheckFailed" from the title.
One additional note, the configuration instruction for the CTT require you to copy the expired certificate to the trusted list for the server, if this is not done then a BadSecurityChecksFailed error is returned, since the certificate is not in the trusted list. It does not matter that it is expired.
Paul Hunkar
Directory of Certification.
Paul Hunkar - DSInteroperability
1 Guest(s)