JanssenProject / jans

An open source enterprise digital identity platform for CIAM or workforce... Janssen is a distribution of standards-based, developer friendly, components that are engineered to work together in any cloud. #OAuth #OpenID #FIDO
https://docs.jans.io
Apache License 2.0
478 stars 75 forks source link

chore(deps): bump org.keycloak:keycloak-services from 25.0.6 to 26.0.6 in /jans-keycloak-integration #10264

Open dependabot[bot] opened 6 hours ago

dependabot[bot] commented 6 hours ago

Bumps org.keycloak:keycloak-services from 25.0.6 to 26.0.6.

Release notes

Sourced from org.keycloak:keycloak-services's releases.

26.0.6

... (truncated)

Commits
  • 5ded193 Set version to 26.0.6
  • 13833fd fix: ensures that properties are runtime properties are filtered (#209)
  • 7bdc16f fix: prevent inclusion of characters that could lead to FileVault path traver...
  • 6a10c0e fix: returning addresses instead of hosts on the ClientConnection (#208)
  • b956819 EMBARGOED CVE-2024-10270 org.keycloak/keycloak-services: Keycloak Denial of S...
  • ba9d0c3 Update docs with security warning around client certificate lookup (#213)
  • c15bc7c Backport to make improvements for translations (#34878)
  • 90bd366 Update installation locations (#34871)
  • 495ddb8 Update Leveraging Jakarta EE (#34901)
  • c27a55d Address QE comments on HA guide (#34902)
  • Additional commits viewable in compare view


Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/JanssenProject/jans/network/alerts).
dryrunsecurity[bot] commented 6 hours ago

DryRun Security Summary

The provided code change updates the keycloak-server.version property from 25.0.6 to 26.0.6 in the jans-keycloak-integration project, which is a routine dependency update that should be thoroughly tested and monitored for any potential security vulnerabilities.

Expand for full summary
**Summary:** The provided code change is updating the `keycloak-server.version` property from `25.0.6` to `26.0.6` in the `pom.xml` file of the `jans-keycloak-integration` project. From an application security perspective, this change is not directly related to any security vulnerabilities or concerns, but rather a routine dependency update. Updating dependencies to their latest versions is generally a good practice, as it can provide bug fixes, security patches, and new features. However, it's important to thoroughly test the application after the dependency update to ensure that the new version does not introduce any regressions or compatibility issues. Additionally, it's a good idea to monitor the release notes and security advisories for the new Keycloak version to be aware of any potential security vulnerabilities that may have been addressed. If any critical security issues are identified, the project maintainers should consider updating the dependency as soon as possible to mitigate the risk. **Files Changed:** - `jans-keycloak-integration/pom.xml`: This file has been updated to change the `keycloak-server.version` property from `25.0.6` to `26.0.6`. This is a routine dependency update and does not raise any immediate security concerns, but the application should be thoroughly tested, and the new Keycloak version should be monitored for any potential security vulnerabilities.

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

:green_circle: Risk threshold not exceeded.

View PR in the DryRun Dashboard.