1. Fixed the issue where protected files wouldn’t open from SharePoint On-Premises in a certain scenario.
a. Before the fix: To open a protected file, when users click on ‘Open with Seclore’ in SharePoint On-Premises and click ‘Use a different account’ in the Seclore authentication page, an error would show up.
b. After the fix: This issue is now resolved.
2. Fixed the issue where the name of the sender (Seclore Admin) wouldn’t appear in the ‘From’ field in some system-generated emails.
a. Before the fix: The ‘From Email ID’ would appear as the name of the sender in the ‘From’ field in some system-generated emails.
b. After the fix: This issue is now resolved.
3. Fixed the issue where some protected emails (.smail files) wouldn’t open in a browser. This issue was observed in Policy Server 3.10.1.0 (Seclore 3.16.1.0) to Policy Server 3.11.1.0 (Seclore 3.18.2.0).
Product Management Team
1. Fixed the issue where protected files wouldn’t open from SharePoint On-Premises in a certain scenario.
a. Before the fix: To open a protected file, when users click on ‘Open with Seclore’ in SharePoint On-Premises and click ‘Use a different account’ in the Seclore authentication page, an error would show up.
b. After the fix: This issue is now resolved.
2. Fixed the issue where the name of the sender (Seclore Admin) wouldn’t appear in the ‘From’ field in some system-generated emails.
a. Before the fix: The ‘From Email ID’ would appear as the name of the sender in the ‘From’ field in some system-generated emails.
b. After the fix: This issue is now resolved.
3. Fixed the issue where some protected emails (.smail files) wouldn’t open in a browser. This issue was observed in Policy Server 3.10.1.0 (Seclore 3.16.1.0) to Policy Server 3.11.1.0 (Seclore 3.18.2.0).