chore(deps): bump bellsoft/liberica-openjre-alpine from 17.0.12 to 23-38 in /docker-jans-configurator

[dependabot]

Bumps bellsoft/liberica-openjre-alpine from 17.0.12 to 23-38.

Most Recent Ignore Conditions Applied to This Pull Request

Dependency Name	Ignore Conditions
bellsoft/liberica-openjre-alpine	[>= 21.pre.37.a, < 22]
bellsoft/liberica-openjre-alpine	[>= 20.pre.37.a, < 21]
bellsoft/liberica-openjre-alpine	[>= 19.pre.37.a, < 20]
bellsoft/liberica-openjre-alpine	[>= 18.pre.37.a, < 19]

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 provided code change updates the Dockerfile for the docker-jans-configurator project, focusing on improving the security of the application by updating the base Java runtime environment, setting up the environment for the "Jans Auth Client" component, syncing assets from a specific version of the "Jans" repository, installing Python dependencies, and configuring various environment variables related to secret management.

Expand for full summary

Summary:

The provided code change is for the Dockerfile of the docker-jans-configurator project. The key changes include updating the base Java runtime environment to a newer version, setting up the environment for the "Jans Auth Client" component, syncing assets from a specific version of the "Jans" repository, installing Python dependencies, and configuring various environment variables related to secret management.

From an application security perspective, the changes appear to be focused on improving the security of the application. The update to the base image helps address known vulnerabilities, the setup of secrets management suggests that the application is handling sensitive information, and the use of a non-root user to run the container is a good security practice. However, it's important to ensure that the dependencies included in the application are from trusted sources and are kept up-to-date to mitigate potential security risks.

Files Changed:

• docker-jans-configurator/Dockerfile: The Dockerfile has been updated with the following changes:
  • The base image is updated from bellsoft/liberica-openjre-alpine:17.0.12 to bellsoft/liberica-openjre-alpine:23-38, which updates the base Java runtime environment to a newer version.
  • The environment is set up for the "Jans Auth Client" component, which is likely used for generating OpenID Connect keys.
  • The "jans-pycloudlib" component is included by cloning a specific version of the "Jans" repository and checking out a specific commit.
  • Python dependencies specified in the requirements.txt file are installed.
  • Various environment variables related to configuration and secret management, such as Consul, Vault, and Google Secret Manager, are set up.
  • A non-root user is created to run the container, which is a good security practice.

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.