chore(deps): bump keycloak/keycloak from 25.0.6 to 26.0.7 in /docker-jans-saml

[dependabot]

Bumps keycloak/keycloak from 25.0.6 to 26.0.7.

Commits

• See full diff in compare view

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 <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)

[dryrunsecurity]

DryRun Security Summary

The code changes in the Janssen Project's GitHub repository focus on improving security practices through structured issue templates, configuration files, and GitHub Actions workflows that emphasize dependency management, access control, and continuous security monitoring.

Expand for full summary

Summary:

The provided code changes cover a wide range of updates to the Janssen Project's GitHub repository, including various issue templates, configuration files, and GitHub Actions workflows. From an application security perspective, the changes generally do not introduce any obvious security vulnerabilities, and in many cases, they demonstrate a strong focus on security best practices.

The key security-related aspects of these changes include:

1. Issue Templates: The new issue templates, such as the bug report, feature request, and failing tests templates, provide a structured way for users to report issues and feature requests. This helps the development team gather the necessary information to investigate and address any potential security-related concerns.

2. Configuration Files: Changes to files like .gitattributes, .github/CODEOWNERS, and .github/dependabot.yml demonstrate a focus on maintaining the project's dependencies, access control, and overall security posture.

3. GitHub Actions Workflows: The various GitHub Actions workflows, such as those for building and testing the application, linting the documentation, and running security scans, show a commitment to continuous integration, testing, and security monitoring. The use of environment hardening, dependency management, and secure credential handling are particularly noteworthy.

Overall, these code changes appear to be part of a broader effort to improve the security and maintainability of the Janssen Project. While there are a few areas that may warrant further review, such as the handling of sensitive information in some of the GitHub Actions workflows, the changes generally demonstrate a security-conscious approach to the project's development and operations.

Files Changed:

1. .github/ISSUE_TEMPLATE/bug_report.md: This file provides a template for users to report bugs, which helps the development team gather the necessary information to investigate and address any issues, including potential security-related concerns.

2. .github/ISSUE_TEMPLATE/development-item.md: This template helps developers track and coordinate their development work, including tasks related to security and code changes.

3. .gitattributes: The changes to this file ensure consistent line endings across different platforms, which is a common practice for maintaining a Git repository.

4. .github/CODEOWNERS: This file defines the default code owners for various parts of the Janssen Project codebase, which can be useful for understanding who is responsible for reviewing and approving changes, including those with potential security implications.

5. .github/ISSUE_TEMPLATE/feature_request.md: This template allows users to submit feature requests, which can help the development team identify and address any security-related requirements or concerns.

6. .github/ISSUE_TEMPLATE/failing-tests.md: This template is designed to help triage and investigate issues related to failing tests, which can be an important part of the security review process.

7. .github/SECURITY.md: This file outlines the Janssen Project's approach to handling security vulnerabilities and how users can report them, demonstrating a commitment to responsible security practices.

8. .github/dependabot.yml: The changes to this file show that the project is using Dependabot to automatically update dependencies, which is a crucial security practice for maintaining the application's security posture.

9. .github/pull_request_template.md: The updated pull request template promotes good practices for code changes and documentation, which can help in maintaining the overall security of the project.

10. .github/maven-settings.xml: This file introduces the use of environment variables for storing sensitive information, which should be carefully reviewed to ensure proper secrets management.

11. .github/workflows/: The various GitHub Actions workflows demonstrate a focus on security-related practices, such as environment hardening, dependency management, and security scanning.

Code Analysis

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

View PR in the DryRun Dashboard.