imbajin opened a new pull request, #806:
URL: https://github.com/apache/hugegraph-toolchain/pull/806

   ## Purpose
   
   Client and Loader HTTPS tests downloaded a pinned public truststore 
containing a certificate that expired in 2023 and has no Subject Alternative 
Name. After Server correctly enforced hostname verification, that fixture could 
not authenticate the HTTPS service at `127.0.0.1`.
   
   The shared test starter now creates a fresh matched key/trust pair for 
`localhost` and `127.0.0.1`. Tests use the truststore from that running 
fixture, with the same wiring for the candidate Server and official 1.7 
baseline. Production TLS verification stays enabled.
   
   ## Changes
   
   - Generate temporary two-day test certificates with the service JDK's native 
`keytool`, and retain only certificates in the client truststore.
   - Pass the runtime truststore path to GitHub Actions tests and the legacy 
Loader Travis caller; support an explicit Maven property for local tests.
   - Include the helper in fixture build inputs and document the test setup.
   - Test real certificate pairing, SANs, validity and HTTPS handshakes, 
including rejection of a wrong hostname; cover both starter layouts and the 
legacy caller.
   
   ## Validation
   
   The shared starter contracts passed, including the real keytool/loopback 
HTTPS and legacy path-transfer tests. The TLS probe also passed with Java 11. 
Client and Loader unit suites and Checkstyle passed on Java 17. Three 
independent reviews and re-review cover the final diff.
   
   The same branch passed the org PR checks, including Client and Loader 
functional CI against the candidate Server and release 1.7, fixture contracts, 
image smoke tests, license checks and CodeQL. Local handshake probes used a 
small JVM HTTPS service.
   
   Org validation: https://github.com/hugegraph/hugegraph-toolchain/pull/59
   
   ## Documentation
   
   Doc - Done: `docs/ci.md`. This changes test fixtures only.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to