Files
nats-server/server
Derek Collison 9de5e3e64d OCSP backports and adds (#4362)
This PR backports the OCSP Peer feature option (as in 2.10 train) and
includes two fixes for the existing OCSP Staple feature.

OCSP Staple: 

1. Fixed and clarified how NATS Server determines its own Issuer CA when
obtaining and validating an OCSP Response for subsequent staple
2. Eliminated problematic assumption that all node peers are issued by
same CA when NATS Server validates ROUTE and GATEWAY peer nodes
3. Added OCSP Response effectivity checks on ROUTE and GATEWAY
peer-presented staple

Note for #3: Allowed host clock skew between node peers set at
30-seconds. If the OCSP Response contains an empty assertion for
NextUpdate, NATS Server will default to 1-hour validity (after
ThisUpdate). It is recommended that CA OCSP Responder should assert
NextUpdate.
2023-08-02 18:10:24 -07:00
..
2023-08-02 11:25:48 -07:00
2023-07-21 16:56:13 -07:00
2023-01-27 10:43:30 +08:00
2022-07-05 09:33:12 +01:00
2023-06-05 13:02:05 -07:00
2022-09-08 11:28:23 -06:00
2023-08-01 21:48:02 -07:00
2022-07-05 09:28:00 +01:00
2022-07-05 09:28:00 +01:00
2023-08-02 11:25:48 -07:00
2022-11-14 08:28:19 -08:00
2023-06-02 13:19:22 +03:00
2023-07-22 20:40:26 -07:00
2023-07-21 16:56:13 -07:00
2023-07-21 16:56:13 -07:00
2023-08-02 11:25:48 -07:00
2023-08-02 11:25:48 -07:00
2023-08-02 11:25:48 -07:00
2023-03-30 15:02:59 -06:00
2023-08-02 11:25:48 -07:00
2023-04-12 11:48:22 -07:00
2023-04-12 11:48:22 -07:00
2023-06-08 15:25:18 +01:00
2023-08-02 08:51:08 -07:00
2023-08-02 11:25:48 -07:00
2023-06-05 22:41:09 +03:00
2023-08-02 18:10:24 -07:00
2023-07-21 16:56:13 -07:00
2022-07-05 09:33:12 +01:00
2022-07-05 09:28:00 +01:00

Tests

Tests that run on Travis have been split into jobs that run in their own VM in parallel. This reduces the overall running time but also is allowing recycling of a job when we get a flapper as opposed to have to recycle the whole test suite.

JetStream Tests

For JetStream tests, we need to observe a naming convention so that no tests are omitted when running on Travis.

The script runTestsOnTravis.sh will run a given job based on the definition found in ".travis.yml".

As for the naming convention:

  • All JetStream tests name should start with TestJetStream
  • Cluster tests should go into jetstream_cluster_test.go and start with TestJetStreamCluster
  • Super-cluster tests should go into jetstream_super_cluster_test.go and start with TestJetStreamSuperCluster

Not following this convention means that some tests may not be executed on Travis.