fix(jans-linux-setup): display CLI logs in jans script

devrimyatar commented 3 days ago

Closes #10202

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

dryrunsecurity[bot] commented 3 days ago

DryRun Security Summary

The provided Python script serves as a wrapper for managing the Janssen Server, an open-source identity and access management (IAM) platform, and should be reviewed for potential security vulnerabilities to ensure its secure implementation.

Expand for full summary

**Summary:** The provided code appears to be a Python script that serves as a wrapper for managing the Janssen Server, an open-source identity and access management (IAM) platform. The script offers various commands to interact with the server, including starting, stopping, restarting, and checking the status of the server's services, as well as viewing log files and other information. From an application security perspective, the script should be reviewed for potential security vulnerabilities, such as improper user input validation, insecure subprocess execution, sensitive information exposure, and the appropriate use of elevated privileges. While the script seems to be well-structured and functional, it's crucial to ensure that it is implemented with a strong focus on security to prevent any potential security issues that could arise from its use. **Files Changed:** - `jans-linux-setup/jans_setup/static/scripts/jans`: This Python script serves as a top-level wrapper for managing the Janssen Server. It provides various commands to interact with the server, such as starting, stopping, restarting, and checking the status of services, as well as viewing log files and other information. The script should be reviewed for potential security vulnerabilities, including: 1. Ensuring proper user input validation and sanitization to prevent command injection. 2. Secure construction of subprocess commands to avoid introducing security issues. 3. Appropriate handling and securing of the configuration file located at `~/.config/jans-cli.ini`. 4. Limiting the exposure of sensitive information, such as the server's hostname. 5. Proper configuration and use of elevated privileges (via the `sudo` command) to only the necessary operations.