CSSCurrent en:Version 7.0.0: Unterschied zwischen den Versionen

Aus Cryptshare Documentation
Wechseln zu:Navigation, Suche
(Updating the cryptshare update process)
(Legacy Archiving Update: making the docs more simpler)
Zeile 27: Zeile 27:


== Legacy Archiving Update ==
== Legacy Archiving Update ==
Legacy archiving functionality, which has been prone to issues and is no longer maintained, has undergone significant changes:
With this release, legacy archiving functionality has been disabled by default to align with our transition towards file-based archiving solutions. It can now only be re-enabled through an advanced configuration property, ensuring that only users with specific needs access this feature. For details on enabling legacy archiving, please visit our [[CSSBackend en:Advanced Configuration|advanced configuration documentation]]. If legacy archiving is currently configured, you may need to reconfigure it during the update process. Information regarding this will be displayed during the update process, guiding administrators on how to transition to supported archiving methods.
 
* '''Feature Flag Introduction''': A new feature flag has been introduced in the properties settings to control the enabling of legacy archiving. (Please contact our support if you need the feature flag to enable Legacy archiving).
* '''Admin Interface Visibility''': Legacy archiving options are now only displayed in the Admin Interface if the feature is actively enabled.
* '''Default Setting''': The feature flag for legacy archiving is disabled by default, reflecting our move towards file based archiving solutions.
* '''Post-Update Notification''': If legacy archiving is configured, information will be displayed on the Post-Update screen. This includes a link to documentation for Local File Archiving, guiding administrators on transitioning to newer, supported archiving methods.


== Additional Changes ==
== Additional Changes ==

Version vom 13. Mai 2024, 14:18 Uhr

Release Date: 13.02.2024

Important Update Notes

Language Packages

Due to structural changes in the language packages, all supported server language packages will be updated automatically, customized language packages will be removed during the update process (a backup is done before). If more language packages are needed, it is required to download and install them again.

In case your language packages have been modified, the attached delta-file Datei:Delta english lp 6.2.0 to 7.0.0.txt can help you to locate the changes in this update and re-apply the modifications. The structure of this file is explained in Language Pack Changes.

Cryptshare Update Process Enhancements

We have updated the Cryptshare update process to improve clarity and functionality. The system now intelligently determines the most suitable update path, considering whether updates can proceed automatically or require manual intervention, and whether they are attended or unattended.

Update Mechanics Explained:

  1. Update Path Selection: The system automatically detects the optimal route for updates. If the latest version requires manual steps, the update process will pause and notify the user. For automated environments, it selects the highest version that allows for an unattended update.
  2. Update Execution: During the update process, Cryptshare handles transitions to ensure continuity. If an update fails, the system automatically reverts to the previous stable version to maintain operational stability.
  3. Notifications and Feedback: Administrators receive notifications about the update status. Alerts are provided for manual interventions and confirmations of successful updates. Notifications about non-critical issues are displayed only to administrators, ensuring they are informed of all pertinent details.
  4. Restoration and Recovery: The system includes safeguards for automatic recoveries and can restore previous configurations if updates affect critical system components.

This approach is designed to provide clarity and improve the manageability of the update process in Cryptshare.

Enhanced Transfer Policy Configuration through CSV

Administrators can now fully configure transfer policies by importing a CSV file. With this update, every configuration input available through the admin web application's wizard can also be set via CSV import. This enhancement provides a comprehensive and efficient method for managing transfer policy settings, ensuring greater flexibility and control.

Improved Validation of Generated Passwords

An issue has been resolved that caused (in rare cases) generated passwords to be rejected because they did match the configured password policies. As part of the solution, the password policy is now checked on saving, to ensure that it allows a sufficient number of secure random passwords.

The password policy is also checked during the update process and may need to be adjusted.

Legacy Archiving Update

With this release, legacy archiving functionality has been disabled by default to align with our transition towards file-based archiving solutions. It can now only be re-enabled through an advanced configuration property, ensuring that only users with specific needs access this feature. For details on enabling legacy archiving, please visit our advanced configuration documentation. If legacy archiving is currently configured, you may need to reconfigure it during the update process. Information regarding this will be displayed during the update process, guiding administrators on how to transition to supported archiving methods.

Additional Changes

  • Enhanced IP Address Configuration in Policy Settings: Policy configurations now support simultaneous IPv4 and IPv6 address inputs, applicable to both direct settings and CSV imports. Validation errors no longer redirect to an error page; instead, the wizard stays open, displaying errors for immediate correction. Additionally, previous issues with IPv6 compatibility have been resolved, ensuring all valid IPv6 addresses are now accepted, improving system reliability and flexibility.
  • Fixed caching issue: We've improved Cryptshare's log file delivery by fixing the issue that the latest files are not downloaded because of cache, ensuring direct access to the latest log files without complications.
  • Update Check Task Improvement: Resolved an issue where not modifying the update URL before running the UpdateCheckTask led to a NullPointerException (NPE). This fix ensures that notifications are sent correctly without errors.
  • JRE Update Enhancements: We've addressed the issue where symlinks were broken due to incorrect POSIX permissions by updating the Java Runtime Environment (JRE). The new JRE update includes an improved handling mechanism that retains the archive format, rather than extracting it, effectively resolving the permissions issue and ensuring symlink integrity.
  • Appliance Settings and Update Checks: Fixed an error that occurred during appliance settings adjustments and refined the REST API to include sender notifications.
  • UI and Styling Fixes: Addressed an issue where large file names disrupted UI styling, and resolved minor XSS vulnerabilities in notification messages for better security.
  • Library Upgrades: Upgraded Java Runtime Environment (JRE) and Spring libraries to enhance performance and security.
  • Admin UI Consistency: Resolved inconsistencies where custom link settings were not properly reflected in the admin UI, ensuring a more reliable configuration experience.