Skip to content

Mutual TLS fails, #79

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
tparkercbn opened this issue Jan 27, 2022 · 1 comment
Closed

Mutual TLS fails, #79

tparkercbn opened this issue Jan 27, 2022 · 1 comment
Labels
duplicate enhancement

Comments

@tparkercbn
Copy link

tparkercbn commented Jan 27, 2022 •
edited
Loading

Describe the bug
Logback TLS doesn't seem to support mutual-TLS when talking to a GELF server that requires a client certificate to be presented.

No test cases. But log4j in the same Tomcat server (different app, same keystore file) connects properly using mutual TLS and logback does not.

logback:

*** ServerHelloDone
Warning: no suitable certificate found - continuing without client authentication
*** Certificate chain
<Empty>
***

log4j:

*** ServerHelloDone
matching alias: development_dev-test_a8devintweb-dev
*** Certificate chain
chain [0] = <redacted contents of my certificate>

Additional context
openjdk version "1.8.0_312"
OpenJDK Runtime Environment (build 1.8.0_312-b07)
OpenJDK 64-Bit Server VM (build 25.312-b07, mixed mode)

SLF4J and Logback version in use.
logback-core-1.2.3.jar
logback-classic-1.2.3.jar
logback-gelf-4.0.0.jar
slf4j-api-1.7.25.jar
@osiegmar
Copy link
Owner

Duplicates #27

@tparkercbn tparkercbn mentioned this issue Jan 30, 2022
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
duplicate enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@osiegmar @tparkercbn