Update suse.md document for package name

[manojs1978]

Prepare

• Read PR guidelines
• Read license information

---

Description

Target issue

closes #issue-number-here
#10438

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 pull request updates the Janssen server installation instructions for SUSE-based Linux distributions, focusing on improving security practices through updated download URLs, package verification, HTTPS configuration, and firewall guidance.

Expand for full summary

Summary:

The changes in this pull request appear to be focused on improving the installation and configuration instructions for the Janssen server on SUSE-based Linux distributions, with a strong emphasis on security best practices. The key changes include updating the download URL and package name, providing instructions for verifying the integrity of the downloaded package using the published SHA256 sum, and guidance on enabling HTTPS communication and firewall configuration. These changes help ensure that the Janssen server can be installed and configured in a secure manner, mitigating potential security risks.

Files Changed:

• docs/janssen-server/install/vm-install/suse.md: This file contains the updated installation instructions for the Janssen server on SUSE Linux Enterprise Server (SLES) 15 and openSUSE Leap 15.5. The changes include:
  1. Updating the download URL for the Janssen server package to use the correct version number.
  2. Updating the instructions for verifying the integrity of the downloaded package using the published SHA256 sum to match the new file name.
  3. Updating the installation command to use the correct package name.
  4. Providing guidance on opening the HTTPS port (443) in the server firewall and enabling HTTPS communication for secure client-server communication.
  5. Documenting the uninstallation process to ensure a clean and complete removal of the software.

These changes demonstrate a strong focus on security best practices, such as secure downloads, firewall configuration, and HTTPS enablement, which are crucial for ensuring the overall security of the Janssen server deployment.

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.