Seclore Online

1. Fixed the issue where protected files wouldn’t open in Lite Viewer in a certain scenario. 

a. Before the fix: When a watermark is configured with a custom font in the Policy Server, protected files wouldn’t open in the Lite Viewer. 

b. After the fix: Files would open successfully, and the watermark would be displayed in the default font. 


2. Fixed the issue where file name would appear incorrectly in the Activity report in a certain scenario. 

a. Before the fix: When a file with special characters in its name is opened in Seclore Online and later unprotected, its name would appear incorrectly in the report downloaded from the Activity tab in the Policy Server portal. 

b. After the fix: This issue is now resolved. 


3. Fixed the issue where open and close activities for a file accessed in Seclore Online would get logged with different files names. 

a. Before the fix: Open activity for a file would get logged with ‘abc.txt.html’ and close activity for the same file would get logged with ‘abc.txt’. 

b. After the fix: This issue is now resolved. 


4. Apache Tomcat upgraded to 9.0.48. 

5. DocumentServer upgraded to version 6.3.1 to improve usability in Seclore Online. 

6. AdoptOpenJDK upgraded to 11.0.11+9. 

7. Made improvements to the Seclore Online Integration Document based on customer feedback.

Login or Signup to post a comment