Policy Server 3.10.4.0
-
Users would now see an enhanced buffer page while opening a Seclore-protected file from a Microsoft Teams channel on Android devices. The buffer page guides users on ways to open the files.
-
Fixed the issue where options to sign in with Google and Microsoft wouldn't work in the Seclore add-in pane in Outlook on the web.
-
Before the fix: An error would show up when users tried to sign in with Google or Microsoft. This issue was observed in Policy Server 3.10.1.0 and later.
-
After the fix: Login options will now appear in a separate pop-up when users click on 'Sign in' in the Seclore add-in pane. Options to sign in with Google and Microsoft will work in the pop-up.
-
Introducing Microsoft Azure single sign-on (SSO) for Seclore add-in in Outlook on the web.
-
Users can now click on 'Sign in' in the Seclore add-in pane and log in using their Microsoft Azure credentials.
-
Thus, users who are already logged in with their Microsoft credentials would be automatically logged in to the Seclore add-in without entering their credentials
Seclore for Mac 3.4.12.0
-
Fixed the issue where the 'Seclore It' button wouldn't appear in Outlook in a certain scenario.
-
Before the fix: The 'Seclore It' button wouldn't appear in Outlook 16.46 due to an architectural change done by Microsoft.
-
After the fix: This issue is now resolved.
Seclore for O365 3.4.0.0
-
Extending automatic protection in SharePoint Online to files already existing in the Document Library.
-
Introducing support for opening Seclore-protected files from Microsoft Teams with the new Seclore tab.
-
This feature is available in Microsoft Teams desktop app and Teams on the web.
-
Here's what the new Seclore tab in a Microsoft Teams channel offers:
-
The 'S' button lets users open, edit, and save Seclore-protected files in the Seclore Online editor if they have the right permissions.
-
Windows 10 users can click on the file name and open, edit, and save the file in the native application.
-
Mac users and other Windows OS users can click on the file name and open, edit, and save the file in the Seclore Online editor.
-
Enhanced Seclore's buffer page with guided instructions on ways to open Seclore-protected files from Microsoft Teams on Android devices.
-
Fixed the issue where files wouldn't get automatically protected in SharePoint Online in certain rare scenarios.
-
Before the fix:
-
When two unprotected files are uploaded to two Document Libraries (DLs) simultaneously, both files get protected as usual. However, when an unprotected file is uploaded to one of the DLs after the simultaneous upload, the file doesn't get protected.
-
After Seclore IRM is enabled in a Document Library, unprotected files uploaded to that library after several days of inactivity wouldn't get protected.
-
After the fix: These issues are now resolved.
-
Apache Tomcat upgraded to 9.0.38.
-
Added support for SQL Server 2019.
-
Upgraded Microsoft Graph SDK to version 2.7.1.
Seclore for Windows 3.13.0.0
-
Introducing support for opening Seclore's HTML-wrapped protected files directly from Microsoft Teams in native applications.
-
This feature is available in Microsoft Teams desktop app and Teams on the web.
-
Windows 10 users can click on the file name in the Seclore tab in Teams, and open, edit, and save the file in the native application. The changes will be synced back to Teams.
-
Users would now see a notification requesting them to sign in to Seclore after they install Seclore for Windows (Admin and Adminless versions).
-
Users who are not logged into Seclore, will be prompted to sign in every time they log into their system.
-
User would see this notification periodically if they've ignored earlier notifications.
-
Users can also use the newly introduced 'Sign in' option when they right-click the Seclore icon in the Windows system tray.
-
The sign-in prompt after installation and the 'Sign in' option in the system tray is available in Windows 7, 8.1, and 10.
-
The periodic 'Sign in' notifications are available in Windows 10 only.
-
Fixed the issue where Seclore-protected files with ampersand in the file name wouldn't open when the user's machine is not connected to the internet.
-
In Seclore for Windows, the 'View File Details' and 'View Activity Logs' options are removed from the Property Sheet of Seclore-protected files. These actions can be performed using the right-click menu.
-
Fixed the issue where HTML-wrapped protected Word and Excel files wouldn't open when opened from the recent files list using File>Open>Recent.
-
Fixed the issue where user authentication doesn't work with some firewalls.
Seclore Online 3.3.0.0
-
Introducing Cloud File Access on Desktop.
-
Added support in Seclore Online to open and edit Seclore-protected files in native applications through Seclore for Windows and Seclore for Mac apps.
-
Added support to save edited files back to the source.
-
Enhanced the error message displayed when users try to open an unprotected file using the 'Open with Seclore' option in SharePoint Online and OneDrive. The message now clearly conveys that unprotected files shouldn't be opened using the aforementioned option.
-
Users would now see Seclore's buffer page while opening a Seclore-protected file from a Microsoft Teams channel on Android devices. The buffer page guides users on ways to open the files.
-
Fixed the issue where protected files with .pptx extension wouldn't open in a certain scenario.
-
Before the fix: Protected files with .pptx extension wouldn't open in the native application once the file is opened from Microsoft Teams in Seclore Online, and thereafter, edited, saved, and closed.
-
After the fix: This issue is now resolved.
-
Fixed the issue where the 'Request Access' feature wouldn't work in a certain scenario.
-
Before the fix: An error would get displayed when a new user opened a Seclore-protected html-wrapped file.
-
After the fix: New users would see the option to request access from the owner after completing authentication.
-
Fixed the issue where Seclore-protected files wouldn't open in Seclore Online if the file name contains curly brackets {}.
Server SDK - Java 4.4.6.0
-
Fixed the issue where IBM JDK wouldn't work with Seclore Server SDK - Java.
Seclore for Android 3.5.0000.0
-
Seclore Lite for Android is now Seclore for Android. The application now appears as 'Seclore' in the Google Play Store.
Seclore for Android-BlackBerry 3.5.0000.1
-
Seclore Lite for BlackBerry is now Seclore for BlackBerry.
Seclore for Android-Intune 3.5.0000.4
-
Seclore Lite for Intune is now Seclore for Intune.
Seclore for iOS 3.8.0000
-
Minor changes made to one of the in-app alerts.
Seclore for iOS-BlackBerry 3.8.0001
-
Minor changes made to one of the in-app alerts.
Seclore for iOS-Intune 3.8.0004
-
Minor changes made to one of the in-app alerts.