We have enhanced the way the keystore password is stored by generating a random key using a proprietary algorithm that will be stored in a separate file in an obfuscated form. This key will then be used at the initialization vector key when decrypting the DB connection properties stored in the property file. A new IV key will be created each time the value is encrypted. The encrypted database username, host and port properties stored in the properties file will each be encrypted with its own IV key.
List of defects reported by customers or implementation, does not contain defects raised internally.
- Fixed password reset change date values when the post import process finds and end_dated account.
- Fixed issue occurring when exporting enrollments from course data format which would result in an infinite loop when the page size is less than 100 and there are more than one page of enrollments.
- Fixed issue occurring when converting a workflow to be stored as XML only when the workflow ends in a hub.
Please sign in to leave a comment.