Skip to content

Comments

Upgrade sasl mechanism for infinispan in tests#21262

Closed
apupier wants to merge 1 commit intoapache:mainfrom
apupier:upgradeSaslMechanismUsedWithInfinispanInTests
Closed

Upgrade sasl mechanism for infinispan in tests#21262
apupier wants to merge 1 commit intoapache:mainfrom
apupier:upgradeSaslMechanismUsedWithInfinispanInTests

Conversation

@apupier
Copy link
Contributor

@apupier apupier commented Feb 5, 2026

with latest upgrade DIGEST_MD5 has been removed, moving to DIGEST-SHA-256

several tests were failing with:

Caused by: java.lang.SecurityException: ISPN004031: The selected
authentication mechanism 'DIGEST-MD5' is not among the supported server
mechanisms: [SCRAM-SHA-512, SCRAM-SHA-384, SCRAM-SHA-256,
DIGEST-SHA-512, DIGEST-SHA-384, DIGEST-SHA-256]

for instance https://ci-builds.apache.org/job/Camel/job/Camel%20Core%20(Build%20and%20test)/job/main/lastCompletedBuild/testReport/org.apache.camel.component.infinispan.remote.spring/SpringInfinispanRemoteIdempotentRepositorySpringIT/BuildAndTest___Matrix___JDK_NAME____jdk_25_latest___PLATFORM____ubuntu_avx____Build_and_test___testIdempotent/

notes:

  • I have not found a constant which would help to detect issue at compile time.
  • tests are often failing locally; usually first run is succesful, next ones are failing

Description

Target

  • I checked that the commit is targeting the correct branch (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 from root folder and I have committed all auto-generated changes.

with latest upgrade DIGEST_MD5 has been removed, moving to
DIGEST-SHA-256

several tests were failing with:
```
Caused by: java.lang.SecurityException: ISPN004031: The selected
authentication mechanism 'DIGEST-MD5' is not among the supported server
mechanisms: [SCRAM-SHA-512, SCRAM-SHA-384, SCRAM-SHA-256,
DIGEST-SHA-512, DIGEST-SHA-384, DIGEST-SHA-256]
```

notes:
* I have not found a constant which would help to detect issue at
compile time.
* tests are often failing locally; usually first run is succesful, next
ones are failing

Signed-off-by: Aurélien Pupier <apupier@ibm.com>
@github-actions
Copy link
Contributor

github-actions bot commented Feb 5, 2026

🌟 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.

@apupier
Copy link
Contributor Author

apupier commented Feb 5, 2026

already fixed with 9f2b4f1

@apupier apupier closed this Feb 5, 2026
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.

4 participants