chore(deps): bump activemq.version from 5.15.16 to 6.1.4 in /jans-auth-server

[dependabot]

Bumps activemq.version from 5.15.16 to 6.1.4.
Updates org.apache.activemq:activemq-client from 5.15.16 to 6.1.4

Commits

• d97f314 [maven-release-plugin] prepare release activemq-6.1.4
• 28b365f AMQ-9617: Adjust consumers timeout to avoid race condition on RestTest
• 535e741 AMQ-9622: Upgrade to log4j 2.24.1
• 9cadaed [AMQ-9530] Fix SelectorAwareVirtualTopicInterceptor ClassCastException if nex...
• 04ab322 AMQ-9621: Upgrade to maven-surefire-plugin 3.5.2
• c65a89a AMQ-9620: Upgrade to maven-javadoc-plugin 3.11.1
• c6c8855 AMQ-9619: Upgrade to groovy 4.0.23
• 1315b55 AMQ-9618: Upgrade to velocity 2.4.1
• e540747 Update spring.schemas version in preparation for 6.1.4 release
• a46edc5 AMQ-9603: Upgrade to Jackson 2.18.1
• Additional commits viewable in compare view

Updates org.apache.activemq:activemq-pool from 5.15.16 to 6.1.4

Commits

• d97f314 [maven-release-plugin] prepare release activemq-6.1.4
• 28b365f AMQ-9617: Adjust consumers timeout to avoid race condition on RestTest
• 535e741 AMQ-9622: Upgrade to log4j 2.24.1
• 9cadaed [AMQ-9530] Fix SelectorAwareVirtualTopicInterceptor ClassCastException if nex...
• 04ab322 AMQ-9621: Upgrade to maven-surefire-plugin 3.5.2
• c65a89a AMQ-9620: Upgrade to maven-javadoc-plugin 3.11.1
• c6c8855 AMQ-9619: Upgrade to groovy 4.0.23
• 1315b55 AMQ-9618: Upgrade to velocity 2.4.1
• e540747 Update spring.schemas version in preparation for 6.1.4 release
• a46edc5 AMQ-9603: Upgrade to Jackson 2.18.1
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[dryrunsecurity]

DryRun Security Summary

The code change updates the activemq dependency from version 5.15.16 to 6.1.4, which is a major version update that requires thorough testing to ensure compatibility and address potential security vulnerabilities.

Expand for full summary

Summary:

The code change in the provided pom.xml file is updating the version of the activemq dependency from 5.15.16 to 6.1.4. From an application security perspective, this change is not particularly concerning, as updating dependencies to their latest versions is generally a good practice to address known security vulnerabilities and bugs. However, it's important to carefully review the release notes and change logs of the new dependency version to ensure that there are no breaking changes or new security issues introduced.

In this case, the change from version 5.15.16 to 6.1.4 of the activemq dependency is a major version update, which could potentially introduce breaking changes. It's recommended to thoroughly test the application after this update to ensure that everything is still functioning as expected. Additionally, it's a good practice to monitor the security advisories and vulnerability reports for the dependencies used in the application, and to proactively update them as new versions are released to address any known security issues.

Files Changed:

• jans-auth-server/pom.xml: This file has been updated to change the version of the activemq dependency from 5.15.16 to 6.1.4. This is a major version update, and it's important to thoroughly test the application after this change to ensure that there are no breaking changes or new security issues introduced.

Code Analysis

We ran 9 analyzers against 1 file and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

View PR in the DryRun Dashboard.

[dryrunsecurity]

DryRun Security Summary

The pull request updates the activemq dependency version from 5.15.16 to 6.1.4 in the pom.xml file, which is generally a good practice to benefit from bug fixes, security patches, and performance improvements, as long as the update is properly tested and validated.

Expand for full summary

Summary:

The code change in this pull request updates the version of the activemq dependency from 5.15.16 to 6.1.4 in the pom.xml file. From an application security perspective, this change is not inherently concerning, as updating dependencies to their latest versions is generally a good practice to benefit from bug fixes, security patches, and performance improvements.

However, it is important to thoroughly test the new dependency version to ensure compatibility with the application and to review the release notes and change logs to understand any security-related changes or fixes that may have been made. As long as the update is properly tested and validated, it should be a safe change to incorporate.

Files Changed:

• jans-auth-server/pom.xml: This file has been updated to change the version of the activemq dependency from 5.15.16 to 6.1.4.

Code Analysis

We ran 9 analyzers against 1 file and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	1 finding

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.