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

[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 Janssen SAML Docker image by upgrading the base image, integrating Keycloak's SAML functionality, synchronizing necessary assets, managing Python dependencies, and implementing security best practices such as using a non-root user and properly handling sensitive information in environment variables.

Expand for full summary

Summary:

The provided code change is for the docker-jans-saml/Dockerfile, which is used to build a Docker image for the Janssen SAML application. The changes focus on updating the base image, integrating Keycloak's SAML functionality, synchronizing necessary assets, and managing Python dependencies and environment variables. From an application security perspective, these changes address several best practices, such as using a non-root user, keeping dependencies up-to-date, and properly managing sensitive information in environment variables. However, it's crucial to thoroughly review the code, dependencies, and configuration to identify any potential security risks or vulnerabilities.

Files Changed:

• docker-jans-saml/Dockerfile: The changes in this file include:
  1. Updating the base image from bellsoft/liberica-openjre-alpine:17.0.12 to bellsoft/liberica-openjre-alpine:23-38, ensuring the latest security patches and bug fixes are applied.
  2. Integrating the Keycloak SAML SPI component, which allows the Janssen SAML application to leverage Keycloak's SAML functionality.
  3. Synchronizing various assets (SQL data types, LDAP schema, and templates) from the Janssen project's jans-linux-setup repository.
  4. Installing Python dependencies specified in the requirements.txt file using pip, which should be reviewed for known vulnerabilities.
  5. Setting environment variables related to configuration, secrets, and persistence, which need to be properly secured.
  6. Creating a non-root user named jans and assigning appropriate permissions, a good security practice.
  7. Setting the entrypoint and command to use the tini process supervisor and the entrypoint.sh script, respectively, for proper application initialization and management.

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.