Skip to content

CAMEL-18962: encryption and signature handling with server config#14311

Merged
davsclaus merged 4 commits into
apache:mainfrom
jonomorris:CAMEL-18962_check_encryption_and_signatures
Jun 4, 2024
Merged

CAMEL-18962: encryption and signature handling with server config#14311
davsclaus merged 4 commits into
apache:mainfrom
jonomorris:CAMEL-18962_check_encryption_and_signatures

Conversation

@jonomorris
Copy link
Copy Markdown
Contributor

Description

When the AS2 server is configured with a decryption key all received messages will require encryption, and only messages with valid encryption will be successfully processed. Similarly, when the AS2 server is configured with a message signature validation certificate chain all received messages will require a signature.

Only messages with valid encryption or signature configured as required will be successfully processed otherwise the server will return an 'insufficient-message-security' error disposition [1].

Additionally messages that cannot be decrypted will return a 'decryption-failed' error, and messages failing signature validation will return an 'authentication-failed' error [2].

[1] https://datatracker.ietf.org/doc/html/rfc4130#section-7.4.3
[2] https://datatracker.ietf.org/doc/html/rfc4130#section-7.5.4

Target

  • I checked that the commit is targeting the correct branch (note that Camel 3 uses camel-3.x, whereas Camel 4 uses the main branch)

Tracking

  • If this is a large change, bug fix, or code improvement, I checked there is a JIRA issue filed for the change (usually before you start working on it).

Apache Camel coding standards and style

  • I checked that each commit in the pull request has a meaningful subject line and body.
  • I have run mvn clean install -DskipTests locally and I have committed all auto-generated changes

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 3, 2024

🌟 Thank you for your contribution to the Apache Camel project! 🌟

🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

  • First-time contributors require MANUAL approval for the GitHub Actions to run

  • You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot.

  • You can label PRs using build-all, build-dependents, skip-tests and test-dependents to fine-tune the checks executed by this PR.

  • Build and test logs are available in the Summary page. Only Apache Camel committers have access to the summary.

  • ⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

@jonomorris
Copy link
Copy Markdown
Contributor Author

jonomorris commented Jun 3, 2024

/component-test as2

Result ✅ The tests passed successfully

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jun 3, 2024

🤖 The Apache Camel test robot will run the tests for you 👍

@davsclaus davsclaus merged commit 00fa693 into apache:main Jun 4, 2024
@jonomorris jonomorris deleted the CAMEL-18962_check_encryption_and_signatures branch September 29, 2024 08:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants