fix(jans-cli-tui): asset issues

[devrimyatar]

closes #9429
closes #9376

• Relevant documentation has been updated if any (i.e. user guides, installation and configuration guides, technical design docs etc)

[dryrunsecurity]

DryRun Security Summary

The pull request updates the "Assets" plugin in the Jans CLI TUI application, improves error handling, and provides documentation for securely managing custom assets on the Janssen Server.

Expand for full summary

Summary:

The code changes in this pull request focus on updating the "Assets" plugin in the Jans CLI TUI (Text-based User Interface) application and providing documentation for managing custom assets on the Janssen Server. The key changes include updating the display name column to show the file name, modifying the asset saving logic, and improving error handling. From an application security perspective, the changes do not appear to introduce any obvious security vulnerabilities, but it's important to ensure that proper input validation, error handling, and security best practices are followed throughout the application. Additionally, the documentation updates related to custom assets management on the Janssen Server highlight the importance of secure implementation, including proper access controls, input validation, and handling of sensitive information.

Files Changed:

1. jans-cli-tui/cli_tui/plugins/130_assets/main.py:

   • The header for the "Display Name" column in the assets list has been changed to "File Name".
   • The logic for saving a new or edited asset has been updated, including changes to the "assetFile" field, "service" field, and the "operation_id" for saving new and editing existing assets.
   • The error handling has been improved, with error messages displayed when the user tries to save an asset without providing a file name and description, or if the asset deletion is not completed successfully.

2. docs/admin/config-guide/custom-assets-configuration.md:

   • The documentation has been updated to provide guidance on managing custom assets using the Janssen Server CLI, TUI, and REST API.
   • The property names have been updated from "displayName" to "fileName" for various asset objects.
   • The code samples demonstrate how to perform various operations on custom assets, such as fetching, adding, updating, and deleting.
   • The documentation highlights the importance of secure implementation, including proper access controls, input validation, and handling of sensitive information related to custom assets.

Code Analysis

We ran 9 analyzers against 4 files and 0 analyzers had findings. 9 analyzers had no findings.

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

[sonarqubecloud]

Quality Gate passed for 'jans-cli'

Issues
1 New issue
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed for 'jans-linux-setup'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[sonarqubecloud]

Quality Gate passed for 'jans-config-api-parent'

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud