Skip to content

Conversation

@gjmwoods
Copy link
Contributor

Adds the ability for TrustStategy to configure whether or not certificate revocation checking is to be carried out. By default revocation checking is disabled.

If enabled with the corresponding server configuration, the driver will check the validity of stapled OCSP (Online Certificate Status Protocol) response(s). These responses are returned during the TLS handshake by the server and if not present, the driver will fail to accept the certificate.

See: https://tools.ietf.org/html/rfc6961

Copy link
Contributor

@michael-simons michael-simons left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great work. There are only some minor changes regarding tests and method visibility.

I also think we should keep the way loading certs through the keystore as opposed to the intermediate suggestion with the TrustAnchors.

As this is for 4.2, we can maybe make the CertificateTool final and add a private constructor too (we tend to do this in OGM and Spring world for those utils classes).

…cate revocation checking is to be carried out. By default revocation checking is disabled.

If enabled with the corresponding server configuration, the driver will check the validity of stapled OCSP (Online Certificate Status Protocol) response(s). These
responses are returned during the TLS handshake by the server and if not present, the driver will fail to accept the certificate.

See: https://tools.ietf.org/html/rfc6961
Copy link
Contributor

@michael-simons michael-simons left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Only typos in JavaDoc.

Copy link
Contributor

@michael-simons michael-simons left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Again, only docs. I remember us discussing this change in standup. I like it very much and its closer to the standard in this way.

@gjmwoods gjmwoods merged commit 16bdde3 into neo4j:4.2 Sep 30, 2020
@gjmwoods gjmwoods deleted the 4.2-ocsp-checks branch September 30, 2020 12:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants