fix(jans-cli-tui): change according to new asset Document schema

[devrimyatar]

closes #9274

• 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 focuses on changes to the "Assets" feature, including renaming fields, input validation, and error handling, but it is important to review the entire codebase to ensure secure coding practices, particularly in areas related to file upload functionality and API interaction.

Expand for full summary

Summary:

The code changes in this pull request appear to be focused on the "Assets" feature of the application. The changes involve renaming several fields in the save_asset and read_asset functions, likely reflecting changes in the data structure or naming conventions used in the application.

From a security perspective, the changes include some positive practices, such as input validation for the 'description' and 'displayName' fields, and error handling mechanisms to provide meaningful feedback to the user. However, it is important to review the entire codebase and ensure that the application follows secure coding practices, particularly in areas related to file upload functionality and API interaction, to mitigate potential security risks.

Files Changed:

• jans-cli-tui/cli_tui/plugins/130_assets/main.py:
  • The key 'jansService' is renamed to 'service' in the save_asset function.
  • The 'jansLevel', 'jansEnabled', and 'jansService' fields are renamed to 'level', 'enabled', and 'service', respectively, in the read_asset function.
  • The code checks if the 'description' and 'displayName' fields are filled before saving the asset, which is a good security practice.
  • The code allows users to upload asset files, and it is important to ensure that the file upload functionality is implemented securely.
  • The code interacts with the application's API to perform CRUD operations on the assets, and it is crucial to ensure that the API endpoints are properly secured and that the application follows best practices for API authentication and authorization.
  • The code includes error handling mechanisms to provide meaningful feedback to the user when a save operation fails, which is a good practice.

Code Analysis

We ran 9 analyzers against 1 file 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
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