Skip to end of metadata
Go to start of metadata


Note on the login process for a pending postupdate

Due to the database changes in the background, the first login process takes longer than usual (up to one minute).


Log in to the administration interface:

Due to changes in the login mechanism there are changes for administrative users.

Login

Administrative users who have existed since a version prior to Crypthshare 4.3.0 and have not logged in until the update to Cryptshare 4.7.0 must be reset by the administrator performing the update in order to log in again.

Changed Archiving Configuration

General

Due to underlying changes, the way how time-based information is processed in the archiving metadata templates has changed. If you previously customized the metadata template for the file-system or SCP archiving connector, please migrate the custom template as described below.


Consequences of omitting this manual step

Please note, that if the archiving meta-data configuration has been adjusted, the update process cannot automatically update this configuration. The migration of this configuration must be done manually after the update has completed. If this manual step is omitted, the archiving meta-data will be incomplete for future transfers.

If this configuration has not been adjusted, it will be updated automatically.

Changed Velocity Context variables

The table below shows all variables which need to be updated with the value listed under New in order to have the same output as before the update.

VariableOldNew
provisionDate
${provisionDate}
${date.toDate(${provisionDate})}
expirationDate
${expirationDate}
${date.toDate(${expirationDate})}

Changed method calls

As a consequence of the changes in above mentioned variables, method calls on these variables have changed as well. The table below shows all method calls which need to be updated with the value listed under New in order to have the same output as before the update.

VariableOldNew
provisionDate
${provisionDate.getTime}
${date.toDate(${provisionDate}).getTime()}
expirationDate
${expirationDate.getTime()}
${date.toDate(${expirationDate}).getTime()}
Table of Contents




Changed System-Log Configuration

Due to changes in the system's structure the configuration file to set the 'system-log' settings will be modified during the post update process. The file resources/logback.xml will be replaced by the a new configuration file.

Backup modified logback.xml manually before the update

If the file resources/logback.xml has been manually modifed, it is advised to make a backup copy of it before starting the update process so its configuration can be applied to the new logback.xml after the update has completed.


Update the logback.xml after post update
  1. Finish the post update procedure.
  2. Navigate in the administration interface to the menu System-Settings → Log Settings→ System-Log.
  3. Copy the contents of the old logback.xml into the input field.
  4. Navigate to the section marked by <!-- Cryptshare logs --> .
  5. Add this line: <logger name="com.cryptshare.server" level="info" />
  6. Click Save changes.

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.

Delta-File for changed passages

In case your language packages have been modified, the attached delta-file delta_english_lp_4.6.1_to_4.7.0.txt can help you to locate the changes in this update and re-apply the modifications.

 Click here to see how the delta file for language packages is built.

Removed Files

Files listed in this section have been removed from the language package entirely.

--------------------------------------------------------------------
REMOVED FILES
--------------------------------------------------------------------
<files>
New Files

Files listed in this section have been added to the language package.

--------------------------------------------------------------------
NEW FILES
--------------------------------------------------------------------
<files>
Modified Files

Files listed in this section have been modified, which can be one of the following cases:

  • Keys have been removed
  • Keys have been added
  • Keys have been modified
--------------------------------------------------------------------
MODIFIED FILES
--------------------------------------------------------------------
-----------------------------------------------------------------
<path and file name>
-----------------------------------------------------------------
------------------
---Removed keys---
------------------
<keys>
--------------
---New keys---
--------------
<keys>
-------------------
---Modified keys---
-------------------
KEY: <affected key>
OLD: <former key & value>
NEW: <new key & value>

In case of a modification, the affected key, its old value and its new value is shown.



  • No labels