Skip to content

Print better errors for CA matching #42970

Open
@strawgate

Description

When we use a trusted fingerprint for our ca, the behavior is very different than using a ca cert.

Let's make this behavior super friendly to users and instead of printing

no CA certificate matching the fingerprint let's add the fingerprint to the log message!

Similarly, if the peer certificate we're looking at does not contain a CA cert, because Elasticsearch's cert is not a full chain, let's print that too.

This way, everyone will be very happy

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    needs_teamIndicates that the issue/PR needs a Team:* label

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions