chore(cloud-native): sync assets for OCI images

[iromli]

Prepare

• Read PR guidelines
• Read license information

---

Description

Target issue

closes #9260

Implementation Details

---

Test and Document the changes

• Static code analysis has been run locally and issues have been fixed
• Relevant unit and integration tests have been added/updated
• Relevant documentation has been updated if any (i.e. user guides, installation and configuration guides, technical design docs etc)

Please check the below before submitting your PR. The PR will not be merged if there are no commits that start with docs: to indicate documentation changes or if the below checklist is not selected.

• I confirm that there is no impact on the docs due to the code changes in this PR.

[dryrunsecurity]

DryRun Security Summary

The provided code changes span multiple Dockerfiles and scripts across various Janssen project components, primarily focusing on updating the build dates, source code versions, and various configuration settings for these components.

Expand for full summary

Summary:

The provided code changes span multiple Dockerfiles and scripts across various Janssen project components, including the Jans Config API, Jans Casa, Jans Certmanager, Jans Configurator, Jans FIDO2, Jans KC Scheduler, Jans Keycloak Link, Jans Link, Jans Monolith, Jans Persistence Loader, Jans SCIM, and Jans SAML. The changes primarily focus on updating the build dates, source code versions, and various configuration settings for these components.

From an application security perspective, the changes do not appear to introduce any obvious security vulnerabilities. However, it is important to review the overall security posture of the application, including the following aspects:

1. Dependency Management: Ensure that all dependencies, including the base Docker images and third-party libraries, are kept up-to-date and do not contain any known security vulnerabilities.

2. Secure Configuration: Review the environment variables and configuration settings to ensure that sensitive information, such as database credentials, API keys, and secrets, are properly managed and secured.

3. Input Validation: Verify that the application properly validates and sanitizes all user input to prevent common web application vulnerabilities, such as SQL injection and cross-site scripting (XSS).

4. Authentication and Authorization: Confirm that the application has robust authentication and authorization mechanisms in place to protect against unauthorized access.

5. Secure Coding Practices: Review the application's source code to ensure that it follows secure coding practices and industry standards.

6. Secure Deployment: Ensure that the Docker images are built and deployed in a secure manner, with appropriate security controls, such as image scanning, network segmentation, and access controls.

Files Changed:

The code changes span multiple files across various Janssen project components, including:

• docker-jans-all-in-one/Dockerfile
• docker-jans-auth-server/templates/jans-lock/clients.ldif
• docker-jans-casa/Dockerfile
• docker-jans-casa/scripts/upgrade.py
• docker-jans-casa/scripts/bootstrap.py
• docker-jans-casa/scripts/entrypoint.sh
• docker-jans-config-api/Dockerfile
• docker-jans-config-api/scripts/upgrade.py
• docker-jans-certmanager/Dockerfile
• docker-jans-configurator/Dockerfile
• docker-jans-keycloak-link/Dockerfile
• docker-jans-link/Dockerfile
• docker-jans-monolith/Dockerfile
• docker-jans-persistence-loader/Dockerfile
• docker-jans-scim/Dockerfile
• docker-jans-saml/Dockerfile

The changes in these files primarily focus on updating the build dates, source code versions, and various configuration settings for the different Janssen project components.

Code Analysis

We ran 9 analyzers against 19 files and 2 analyzers had findings. 7 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	14 findings
Authn/Authz Analyzer	2 findings

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.