Add mutual TLS (client certificate) authentication for outbound HTTPS#558
Open
JakeHuneau wants to merge 1 commit into
Open
Add mutual TLS (client certificate) authentication for outbound HTTPS#558JakeHuneau wants to merge 1 commit into
JakeHuneau wants to merge 1 commit into
Conversation
Partners requiring TLS client certificate authentication on their AS2 endpoints (e.g. when migrating from Cleo Harmony) can now be sent to by configuring these partnership attributes, with fallback to properties for a global client identity: - https_client_keystore: PKCS12 (or .jks) file holding the private key and certificate chain to present - https_client_keystore_password - https_client_cert_alias: optional selection of a specific key entry when the keystore holds more than one The client key material is wired into all three SSL trust paths in HTTPUtil.buildSslFactory (system default, custom self-signed trust store and overridden SSL checks) and flows from AS2SenderModule and MDNSenderModule so messages, async MDNs and resends are all covered. Combines with existing http_user/http_password basic auth. Tested with a client-auth-required HTTPS server using certificates generated at test runtime plus a live OpenAS2 server run verifying the certificate is presented and that sends fail without it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Partners requiring TLS client certificate authentication on their AS2 endpoints can now be sent to by configuring these partnership attributes, with fallback to properties for a global client identity:
The client key material is wired into all three SSL trust paths in HTTPUtil.buildSslFactory (system default, custom self-signed trust store and overridden SSL checks) and flows from AS2SenderModule and MDNSenderModule so messages, async MDNs and resends are all covered. Combines with existing http_user/http_password basic auth.
Tested with a client-auth-required HTTPS server using certificates generated at test runtime plus a live OpenAS2 server run verifying the certificate is presented and that sends fail without it.