Networking Software. Trending from CNET. Visit Site. Contact publisher to get the pricing information and to request a demo. Developer's Description By Seclore technologies. Seclore FileSecure empowers individual users to be in full control of the documents' usage for documents owned by them.
After creating the document, the Owner can set specific usage rights for specific users and distribute the document with full confidence that the usage rights will be applied on the document every time it is accessed, regardless of where the document or its copy is physically present.
Full Specifications. What's new in version. Release October 16, Date Added October 16, Operating Systems. Operating Systems Windows. Additional Requirements None. Total Downloads Downloads Last Week 1. Report Software. Related Software. Vpn One Click Free to try. Protect your privacy online and unlock all blocked services.
Protected Folder Free to try. Password-protect your folders and files from being seen, read or modified. Random Password Generator Free. Create and manage secure and strong passwords. Cryptomator Free. Protect your documents from unauthorized access. Before the fix: HTML-wrapped files in shared folders on a network wouldn't open when dragged and dropped on Chrome with the intent of opening them in the native application using the 'Open Seclore' button. Changes to make Seclore Online a completely independent agent of the Policy Server for better scalability and performance.
Seclore Online is now an independent offering that opens Seclore-protected files online without processing them in the Policy Server. Seclore Policy Server upgraded to Apache Tomcat 9. Now, this feature is disabled by default for all enterprises with Seclore for Windows 3. To enable this feature, it will need to be explicitly enabled during the installation or upgrade process. Fixed the issue where downloading the Seclore agent from Seclore Online Editor would show an error in certain rare scenarios.
This impacts only older HTML-wrapped files. Language Pack upgrade for Spanish, French and Russian. Seclore for 3. It lets you open Seclore-protected files from Microsoft Teams in Seclore Online, edit, and save it back. This feature is supported in the Windows and Web application of Microsoft Teams. Now, this feature is disabled by default to allow enterprises to work seamlessly with third party classification solutions; however, it can be enabled if enterprises need it.
Fixed the issue where protected files wouldn't open in certain rare scenarios. Before the fix: Protected files wouldn't open from a location where the file path along with the file name would exceed characters. Earlier, Seclore Online used the Policy Server to open Seclore-protected files in the secure browser-based editor or viewer.
Now, Seclore Online can do it independently. This requires Policy Server version 3. Seclore Online no longer supports SSL 3. Apache Tomcat for Seclore Online upgraded to 9. Seclore Lite for Android 1.
With this release, we have discontinued support for Android 7. Seclore Lite for BlackBerry in Android 3. Seclore Lite for iOS 3. Now, you can login to the Seclore agent on Windows with your default browser.
While logging in you'll be directed to an authentication page on your browser. All other login features remain the same. Fixed the issue where protected PDF files wouldn't open in certain rare scenarios. Fixed the issue where a Seclore message shows the file path instead of the file name in certain rare scenarios. Before the fix: Upon trying to edit and close a Seclore-protected file with only 'Read' permission, Seclore shows a message telling the user that they do not have permission to edit the document.
This message would show the file path instead of the file name. Fixed the usability issue where the Policy Server name would reflect incorrectly in the 'About' dialog box of the agent. Enterprises can now use Azure AD for both authentication and authorization services in Seclore.
Seclore Policy Server directly connects to the Microsoft Azure cloud service, and no longer needs to connect to the on-premise AD. All Seclore features like user provisioning, assigning user permissions, assigning user licenses, etc. This feature is available for internal enterprise users of the organization. Enhanced authentication with Microsoft Azure AD for external users. Earlier, only internal users in the organization's Azure AD could authenticate in Seclore using the 'Sign in with Microsoft' option.
Now, all external users can authenticate with their personal, work, or school account. Seclore Azure tool to be no longer available in the Policy Server package. Before the fix: The Seclore Azure tool would display an error when opened.
After the fix: The tool is deprecated, and manual steps will be provided to register the Seclore Azure application. Repository Adaptor Migration Tool 1. This tool updates the user ID references in the Policy Server. Messages are now wrapped with a more intuitive layout to enhance usability. Added support to retain classification metadata information in Seclore-protected files when they are edited and saved using the Seclore agent.
Fixed the issue where Outlook was shutting down unexpectedly in certain rare scenarios. Before the fix: Outlook would shut down randomly, when composing an email in RTF Rich Text Format format and attaching another Outlook email or any Outlook item as an attachment. After the fix: Protecting an email in RTF format with any Outlook item as an attachment, now works as expected. Fixed the issue where the Word app shuts down unexpectedly in certain rare scenarios. Before the fix: Word would shut down unexpectedly when a user selects some text in a protected Word document and then clicks elsewhere while another unprotected document was open in the background.
This issue occurs only in Office version Build Fixed the issue which occurs in Seclore-protected Excel files in certain rare scenarios.
Before the fix: When opening a Seclore-protected Excel file that has reference links to any other file, it works the first time, but doesn't work on the 2nd attempt. This happens with standalone Office or versions only, but not with O versions.
Fixed the issue of "Sign in with Microsoft" not working when proxy is enabled. Before the fix: An error page is displayed while signing in with Microsoft when proxy is enabled. After the fix: "Sign in with Microsoft" is successful, and the error is no longer displayed even when proxy is enabled. Fixed the issue of inconsistent signatures in email notifications. Before the fix: Users were encountering an unexpected error while opening protected files from SharePoint Server using Seclore Online.
Added support to retain classification metadata information in HTML buffer file when protected documents are edited and saved with Seclore Online. Data Protection Portal 3. Added support for Tomcat 9. This new universal email decrypter can be integrated with any on-premise or cloud-based email service to decrypt Seclore protected emails for content inspection.
It can decrypt emails that are sent outside the enterprise domain. It ensures email is decrypted only for the content inspection solution to inspect sensitive content and delivers the same original protected email to all recipients. Seclore for Boldon James 3. Before the fix: Content discovery solutions like DLPs were unable to read classification metadata for documents protected using classification-driven protection with Boldon James.
After the fix: Now, DLP or any other discovery solution can read classification metadata for documents protected using classification-driven protection. Now, documents once classified and protected will get HTML wrapped automatically. Requires Policy Server 3. Added support for Mac Operating System. Desktop Client 3. Before the fix: When the user closed a MS PowerPoint file, the save intimation popup that appears displays the location of the file rather than the file name.
After the fix: Now When the user closes a MS PowerPoint file, the save intimation popup that appears displays the file name. Fixed the authentication issue that arises due to difference in time between the client and server machine. Before the fix: If there was a time difference between client and server machines, user authentication would fail intermittently.
After the fix: Now if there is as time difference between client and server machines, user authentication will not fail. Seclore for macOS 3. Before the fix: When an unprotected Office file is opened from OneDrive online or a sync agent location, edited, and saved, an "Upload failed" error used to show up. Consequently, the edits were not saved.
After the fix: Such files are now saved without any error and the edits are uploaded to the online repository. Hot Folder Server 3. Earlier, when Hot Folder Enterprise Manager was launched, Add and Edit buttons were always in disabled state under the credentials section.
Now, these unused buttons have been removed. Before the fix: MS Office files protected without html wrapping, when opened from the local One Drive Sync folder fail to open in Standalone Office The issue is observed only for natively protected files and not HTML wrapped files.
After the fix: The protected file should open without any issue. Seclore presents the "Seclore It" button in all Microsoft Office apps for single-click protection from within the open file. User can enable the button while editing an unprotected document.
Once the user closes the unprotected file with the Seclore It button enabled, the file gets protected and the user is prompted to change the file permissions and add recipients. File permissions can also be added to the protected file while emailing, using Smart Sharing. Extending Seclore's email protection capability to third-party tools. Third-party tools can now integrate with Seclore's email protection interface in Outlook allowing them to leverage end-to-end security for emails and attachments in collaboration with their product features.
Now files protected using Universal Protection will open directly in the edit mode when opened using the native app. Users can edit and save changes directly in such files without the need for unprotecting and opening them in the native app for editing. This is useful in scenarios where the Seclore Protected file is opened in a 3rd party viewer that cannot render HTML content.
Fixed the issue where the PS login page was displayed instead of a prompt asking the user to allow login using the credentials logged into the Desktop Client. Instead the PS Login page was displayed, and the user had to login again using his credentials. After the fix: Now the user will be directed to the SSO prompt allowing to login directly using the Desktop Client login. This is useful in scenarios where the Seclore protected file is opened in a 3rd party viewer that cannot render HTML content.
When you close the file, the HTML wrapping is preserved. The closed HTML wrapped file will be the latest version. If you close an HTML wrapped protected file opened in Microsoft PowerPoint after editing, the Save dialog box prompts you to save the file before closing the application.
Fixed the issue where an error was displayed on saving unwrapped protected PowerPoint files after editing. Fixed the issue where while opening protected word and excel files, an error was displayed if Seclore login took more than 20 to 30 seconds. This new role allows administrators to manage key security features like Enterprise Application integrations, Hot Folder Cabinets, Classification labels, rules in Email Auto-Protector etc.
Admins configured to manage all enterprise user repositories would be able to manage these key security features All other admins managing a specific organizational unit will continue security policies for thier assigned OU Incorporated the new HTML buffer file, that displays user instructions for file open in the raw HTML content.
Fixed the issue where a protected file opened even after the user logged out of the client instead of prompting the user to log in. Enhanced the speed of opening and protected files. Earlier, while installing Hot Folder Server, the installer checked if Seclore Desktop Client was installed in the system or not.
Now, this check is removed. This is useful in scenarios where Seclore Protected file is opened in a 3rd party application that cannot render HTML content. Seclore O Service - 3. Introduced multithreading in file protection flow. With this, multiple files will be processed together for protection resulting in improved multi-file protection time.
The new API provides more accurate results and helps Seclore connector to get hold of the file earlier to protect it after upload. Changes to support multitenancy of Seclore online. Currently, there is one to one mapping between policy server and Seclore online component. With introduction of multitenancy in Seclore online part of roadmap , single Seclore online would be able to support multiple policy servers.
Fixed the issue where, in some cases, the first file uploaded after the Document Library was Seclore IRM enabled, was not getting protected. Before the fix: In some instances, the first file upload after IRM enabling the document library was not getting protected.
After the fix: The first file that is uploaded will now be protected in all the cases. Updated support for Database to be in sync with other components. Fixed the issue where a protected file was incorrectly named after convert to native and unprotect actions on the file.
Before the fix: When a protected file was renamed and converted to native format, the resulting file was named incorrectly. Similarly, when a protected file was renamed and unprotected, the unprotected file was named incorrectly. After the fix: The files will be named as expected even after renaming and Convert to Native and Unprotect actions. Fixed the issue where while opening protected files with names in some languages other than English, an error was displayed.
Before the fix: When a protected HTML-wrapped file with name in few specific languages other than English is opened, an error was displayed. After the fix: The file will open successfully. Fixed the issue where error was displayed when an already opened protected file from a network location is opened again. Before the fix: When an already opened protected file from a network location is opened again, an error was displayed.
After the fix: The file will open in read-only mode in this case. Now there is no need for an IT admin to intervene while installing and operating the Adminless version for Desktop Client on Windows This client will provide all the capabilities that are available for the agent in the Admin mode.
The option to download both the modes of Desktop Client will be available in the Policy Server version 3. Additionally, when you click the Download the Seclore app option in the buffer file for agentless access, you will be prompted to download the Adminless Desktop Client instead of Seclore Lite for Windows.
On updating Seclore Lite for Windows version 3. Introducing the capability of printing the watermark over large images in protected PDF files. In case of protected PDF files containing large or scanned images, printing the files with the watermark behind the image makes the purpose of the watermark redundant. Seclore has enabled the capability of printing the watermark over the content and images of a protected PDF file, if the PDF file contains large images.
This percentage of page size is set by default. The percentage can also be configured as per requirement. If the protected PDF files do not contain large images, the watermark will appear behind the content and smaller images on printing.
This feature will be disabled in the Desktop Client, by default. Fixed the issue where watermark was not displayed for decrypted in-line protected email body in Outlook. Before the fix: If the user was logged in to the Desktop Client and had access to a protected email body, the email was displayed in-line in Outlook without the watermark. After the fix: The decrypted in-line email body with the watermark will now be displayed for protected emails. Fixed the issue where the buffer file was not properly displayed when an HTML-wrapped file was opened in the browser for the first time.
Before the fix: When an HTML-wrapped file was opened in a browser, the buffer file was not displayed properly. Instead an error message was displayed stating that the client was unable to connect to the Policy Server. After the fix: The buffer file will be displayed successfully. Fixed the issue where in certain cases Outlook stopped functioning when user forwarded or replied to unprotected emails containing inline attachments. On clicking No, Outlook stopped functioning.
This was observed when Desktop Client of version 3. This happens when inline attachments are not downloaded before Reply or Forward action After the fix: Outlook will remain functional and the email will be forwarded, or the reply will be sent successfully.
For files protected using Advanced Protection: Now, when you open an HTML wrapped protected file by double-clicking on it, it will open in the native application.
After editing in the native application if you click Save, the content is updated in the HTML wrapped file itself. If you close an HTML wrapped protected file opened in the native application after editing, the Save dialog box prompts you to save the file before closing the application.
For such formats,. The user will be able to make changes to the file by saving it locally using "Save As". However, on saving after changes, the Save As dialog box appears. On saving, an unprotected file is saved on your machine.
Fixed the rare issue where in certain cases Microsoft Office applications stopped functioning on opening in the presence of Seclore for Mac.
Before the fix: When a user opened any Microsoft Office application, it stopped functioning instead of opening successfully. This was observed in certain systems with macOS After the fix: The Microsoft Office applications will now open as expected.
The user has an option to download and install either Admin or Adminless mode of the new agent. Now there is no need for an IT admin to intervene while installing and operating the Adminless version for Desktop Client on Windows. This client will provide all the capabilities that are available for the agent in the Admin mode.
Updated the logos and subtitle text for the existing Branded Enterprise Application option. Before this change, a logged in user, on clicking sign out, was redirected to the Sign in page. Now, a logged in user, on clicking Sign out, will be redirected to the newly introduced screen. This screen will inform that the user has successfully signed out from the Seclore Policy Server.
It also displays a Sign in again button. On clicking this, the user will be redirected to the Sign in screen where user can sign in again to the Policy Server. The above-mentioned flow is applicable to System Admins as well.
In cases of SSO integration, clicking on Sign in again will redirected the user to the SSO solution which the user had used to login earlier. If the user is already authenticated in the SSO system, the user will be logged in automatically on clicking on Sign in again.
Fixed the issue where the Seclore plugin had stopped working in Outlook Web App. Before the fix: When a user clicked on the Seclore It! Due to this error, user was unable to drag and drop documents and protect them using Seclore on OWA. After the fix: The panel opens as expected and users can successfully add and protected files before sending them using OWA. Added the capability of automatically onboarding a new user in Seclore SIM , at the time of file open through Seclore Online Integration, if the user has permissions on document through Policy Federation, but the user does not yet exist in Seclore SIM.
Fixed the rare issue where the user was asked to login for every activity on the Policy Server if the user logged in using the Microsoft option from the Desktop Client. Before the fix: When a user logged in using the Microsoft option on Desktop Client, and tried to perform different activities, the user was prompted to login before every activity. This was observed in certain cases. After the fix: User can now successfully login using the Microsoft option on the Desktop Client once and perform all the activities without being prompted to login repeatedly.
Updated the Policy Server Installation guide with the latest information. System upgrades. Once a Document Library is enabled for Automatic protection, every document uploaded in, moved to or created within the Document Library will be automatically protected Policy Federation will ensure that permissions defined in SharePoint Online get automatically extended to the Seclore-Protected documents even after they are download and accessed or shared.
If use's permissions are changed or revoked in SharePoint Online, the same would be reflected on the downloaded or synced copies of the document. This ensures that there is a single source of truth for document security in SharePoint Online. Users can securely share documents with internal and external users, through Automated protection and Policy Federation capabilities, without separately defining Security Policies in the Seclore Policy Server.
Before the fix: When a HTML wrapped protected file was opened in a browser, an error message was displayed instead of the buffer file due to delay in response from the Policy Server. After the fix: While opening a HTML wrapped protected file in the browser, the buffer file is successfully displayed without any error.
For a Seclore-protected document, users with Edit permissions on Word documents can save it after editing by using the shortcut F12 key from the keyboard. Before the fix: When a user, with Edit permission, tried to save a protected Word document using the F12 shortcut key, an error was displayed. After the fix: A protected Word document can now be saved as a new file using the F12 shortcut key. Fixed the rare issue where Microsoft Outlook stopped functioning when an email containing Microsoft AIP protected attachments and inline attachments was selected in the inbox.
Before the fix: When a user selected an email containing Microsoft AIP protected documents and inline attachments, Outlook stopped functioning. This also occurred when Outlook is started and there are emails of the above-mentioned nature in the inbox. After the fix: When such emails are selected, Outlook will work as expected. Fixed the issue where a newly added signature was not saved in a protected PDF file.
HotFolder Server 3. This issue was not observed with non-wrapped protected files. After the fix: All files protected using Hot Folders created in any drive of a machine including the C: drive can be opened successfully. If the original unprotected or protected file was placed in the same Hot Folder again, a replace prompt was displayed.
After the fix: When a HTML wrapped file is deleted from a Hot Folder and the original file is placed again in the same Hot Folder, the replace prompt will not be displayed. Now, when you open an HTML wrapped protected file by double-clicking on it, it will open in the native application. This works on all file formats with the exception of image and text file formats. Fixed the issue where incorrect error messages in the local language of the user was displayed on opening a file in certain cases.
Before the fix: Incorrect error message for invalid PS certificates while opening a file, was displayed in the local language of the user.
After the fix: The correct error message in English will be displayed in the above-mentioned case. Fixed the issue where if a file with read permission was opened from a network location, another file from the network failed to open.
Before the fix: The user opened a protected file from a network location with read permission. When the user tried to open another protected file of the same native application from a network location, it failed to open. After the fix: Protected files from network locations open successfully one after the other.
Discontinued support for Adobe Reader X. Once you receive a universally protected file on email, click on the protected attachment HTML-wrapped. You will be prompted to open it with any of the applications in your device. Select Seclore for iOS app. Post authentication, the user will be asked to select a native application that supports the file. Fixed the issue where password protected files did not open on iOS devices.
Before the fix: When a protected file, with password protection, was opened in Seclore for iOS, the file did not open. After the fix: A prompt will ask for a password when such files are opened.
After the user enters the password the file will open. The user will require Seclore Full control permissions on the file to see this option in the Seclore Online Editor. HotFolderServer 3. Earlier, non-standard file formats were protected and given. Files protected with. The files previously protected and given. Requires i. Policy Sever version 3. This will remove the additional step of HTML wrapping a file after protecting it.
To convert an HTML wrapped file to the native format, 'Convert to native format' option is added in the right-click context menu. This feature will not be available in the presence of Boldon James classification or Seclore-classification based protection. Files with non-standard formats were not protected. These files will be protected with full control to the authorized user and they will be HTML wrapped automatically after protection.
When user logs in on the Policy Server or agents, the 'Terms of Service' and 'Privacy Policies' will be available to the user to view. These will inform the user of the kind of information Seclore will collect and how it will be used. If the user agrees, they can enable the check box on the login page and proceed to login.
Fixed the issue when a protected Word or Excel file was saved as unprotected when saving to OneDrive using the AutoSave option.
Before the fix: The user opened a protected Word or Excel file with less than Full Control permission. When the user clicked the AutoSave option and configured it to be saved on OneDrive, the file was saved as an unprotected file.
Made the error messages informative in case the Seclore agent is not able to process a user action. Now the user will be able to know the nature of the error from the error message itself.
This will help the users and system administrators to resolve the issue at the earliest for uninterrupted use of Seclore. Fixed the issue where the Seclore icon was not visible on the taskbar when the agent was active on the Desktop. Before the fix: The Seclore icon on the taskbar appeared black when the agent was active on the Desktop. After the fix: The Seclore lock icon will be visible on the taskbar when the agent is active on the Desktop.
Fixed the issue where the users with no access or expired access could view the buffer file or the data itself after RAR. Before the fix: For a user who did not have access to a protected file, the RAR dialogue box appeared. After the user requested access permission to the protected document, the buffer file was displayed.
For a user with expired access, after RAR the document opened with the data. After the fix: After RAR, in both the scenarios mentioned above, the document will close. Users will have access to the document and can view it only after the owner of the protected file assigns or renews permissions. If Seclore agent is not available, the file opens in Seclore Online.
Introducing Universal Protection for Endpoint protection. Earlier, files with standard formats were discovered by Endpoint and protected using Seclore. After this release, non-standard file formats will be protected using Universal Protection when discovered by Endpoint scanner.
These policies will inform the user of the kind of information Seclore will collect and how it will be used. Fixed the issue where a new Word document was saved as a protected file when created after opening a protected Word document.
Before the fix: The user opened a protected Word document. The new document opened with the same watermark as the open protected document. On editing and saving the new document, it was saved as a protected document.
After the fix: The new document will be created without a watermark and will be saved as an unprotected document after edit and save. Policy server 3. When user logs in on the Policy Server, the 'Terms of Service' and 'Privacy Policies' will be available to the user to view.
Introducing the capability of downloading an unprotected copy of a protected file open in the Seclore Online Editor. When a protected file is opened in the Seclore Online Editor and the user clicks on the download icon, 'Download Unprotected Copy' option will be available in the drop down.
On selecting this option, the unprotected copy of the file will be downloaded. This option will be available only if the 'Download Unprotected' flag is enabled in the Policy Server. The user must also have Full Control on the protected file to download an unprotected copy. Fixed the issue where error page was displayed in certain cases when the user tried to login to the Policy Server using Microsoft credentials.
Before the fix: When the user opened a protected file from Microsoft application like SharePoint Online, an error page was displayed when Microsoft based authentication was either disabled or not configured.
After the fix: The Policy Server login page will now be displayed in the above-mentioned scenario. Added support for Oracle 18c and 19c database versions.
This was observed with the Desktop Client version 3. For standard file formats i. Fixed the issue where the Undo action did not work after editing and saving a protected Excel file. Before the fix: After a user opened, edited and saved a protected Excel file, the Undo action did not work like it should in case of an unprotected Excel file. After the fix: Undo changes can be performed even after saving changes in a protected Excel file.
Fixed the issue where a protected file lost all the attributes after it was HTML wrapped. These attributes included Read Only mode, hidden attribute, change in creation date, etc. Fixed the issue where in case of cloned Windows machines, the installation report of the Seclore Desktop Client displayed only a single entry.
Before the fix: When a machine was cloned and Desktop Client was installed in the cloned machine, it replaced the installation entry of the previous machine. Due to this, the installation report did not record the actual number of installations of the Seclore Desktop Client.
After the fix: The installation report will display the installation of Desktop Client in the cloned machine as a separate entry. This will ensure that the actual number of installations of the Desktop Client is recorded in the installation report. Before the change: Seclore provides five default classifications. User can create new classifications in the Policy Server and protect files using these classifications When the user changed the permission on such files as mentioned in the above point, an error is displayed.
After the change: User can change permission on any protected file with any classification without any error. Fixed the issue where the installation report displayed only a single entry for machines with same SID. Fixed the issue where the direction of Arabic text in Seclore Online Viewer did not appear properly.
Before the change: Arabic text is written from right to left unlike other languages that are written from left to right. When a document written in Arabic and protected was opened in Seclore Online Viewer, it's direction and orientation did not appear as expected.
Fixed the issue where disk space was getting used up when files were accessed through SharePoint. Before the change: When protected files were opened through SharePoint, disk space was getting used up and a warning was displayed. This was rectified after the application was restarted. After the change: Now user can open and work on protected files from SharePoint without encountering disk space warning messages. Now all PS based message will be displayed in the language configured for the user.
Lite for Mac 3. Before the change: When a user sends an email with an attachment that fulfills certain rules, it is routed through the Seclore Email Auto Protector.
The Email Auto Protector either protects or unprotects an email depending on rules set in the rules console. When the recipient searches their mailbox using a keyword, the emails routed through Seclore Email Auto Protector did not appear in the results even if they fulfilled the search criteria.
After the change: Emails routed through Seclore Email Auto Protector will appear in the results if they fulfill the search criteria. With this new feature, users can now protect any file format on their desktop or in Outlook. Authorized recipients can also Unprotect these files. The Policy Server also supports Agentless Access for these files, that allows authorized users to get an unprotected copy of the document without using an agent.
End of Advanced Protection support for certain outdated file extensions. Certain file formats will not be supported by Seclore for Advanced Protection, going forward. These file formats will be included under Universal Protection and the permissions granted for Universal Protection will be applicable.
When the Policy Server is updated and the Desktop Client is not updated, files in these formats, which were previously protected using Advanced Protection, will continue to grant the previously applied permissions.
When the Desktop Client is updated, files in these formats, which were previously protected using Advanced Protection, will prompt the user to get the file re-protected using Universal Protection from the owner on access. This is regardless of the Policy Server being updated or not. Fixed the issue where the PowerPoint files protected and unprotected stopped functioning when a user moved through a list of files in the File Explorer with the Preview Pane enabled.
This particular behaviour was not observed for other Microsoft Office file formats as preview is disabled for file formats like Word and Excel. After this change: PowerPoint files will function and remain open as expected even with the Preview Pane enabled in the File Explorer. Fixed the issue where the default browser icon was displayed for a HTML wrapped file. Instead, the default browser for example, Chrome icon was displayed. This usually occurred after restarting the system.
Exception: Files with. Fixed the issue where the default file format icon was not displayed for HTML-wrapped files when a copy of the file was created or when an HTML-wrapped file was downloaded multiple times. Instead, the default browser icon was displayed. Fixed the issue where the lengthy email IDs of the file owners spilled over the permission widget of an open protected file.
Before the change: When the user clicked the 'S' button in an open protected document, the email ID of the owner spilled over the permission widget. After the change: For lengthy email IDs, part of the email ID is visible, and three dots are added after that.
The user can hover over the dots and view the complete email ID as a tooltip. Fixed the issue where Outlook stopped functioning when the user clicked on the 'Seclore It' button for protecting emails and attachments.
Before the change: While composing an email from the Outlook application when the user clicked on the 'Seclore It' button from the Menu ribbon, Outlook stopped functioning. This issue was observed for users with Policy Server version 3. After the change: When the user clicks the 'Seclore It' button on the Menu ribbon in the Outlook application, the Seclore options will be displayed, as expected.
Seclore Lite for Mac 3. Before the change: When the HTML wrap feature is disabled in the Policy Server, if the user invokes the 'Seclore It' option in Outlook, the email and attachments are always sent unprotected.
After the change: In this scenario, attachments will be sent protected, as expected. Fixed the issue faced where creating a new Microsoft Excel workbook from a template was not working as expected. Before the change: When the user created a new Workbook from a template, the application would shut down unexpectedly. After the change: This issue has now been fixed.
Fixed the issue where a protected and HTML-wrapped file got unwrapped if an unauthorized user unprotects it. Fixed the rare issue where certain file formats docm, docx, xlsm and xlsx were not getting protected from a network shared folder. After the change: The files get protected, as expected.
Fixed the issue where protected files placed on network shared folders were not getting converted to Agentless format HTML-wrapped. Fixed the rare issue where the Seclore operations returned an error message when performed on some network shared folders.
Fixed the issue where the agent becomes unresponsive if the user tries to protect a file that is already open. The agent also became unresponsive to any further commands. After the change: The file gets protected and the agent works as expected. Introducing collaboration of MS O and Seclore for enhanced security of your documents on the cloud. Now, you can edit and save your changes if you have the required permissions in the documents shared through SharePoint Online and OneDrive. External users can also edit documents if they have Edit permission from the document links shared with them.
The look and feel of the new Seclore Online Editor are similar to the corresponding Microsoft Office applications. Important functional buttons such as Save, Print, Undo and Redo are moved to the Only Office title bar for better visibility.
In addition to the Only Office title bar, another title bar will be visible for Seclore-protected documents. This new title bar will display the customer logo, Read-only in case of read-only files , Edit button for integration workflows and the download button.
The Edit button appears only when a file is opened in the Read-only mode in case of integration workflows like opening protected files from SharePoint online.
The Edit button is not visible in the Edit mode. For non-integration workflows, documents open in the view depending on the granted permission. The download button is moved from the inside of the document to the Seclore title bar. In Read-only mode, only the option to download the Seclore agent is visible on clicking the download button. In Edit mode, the options to download the Seclore agent and to download the protected copy of the file.
Now, the online help package is released separately from the Policy Server package and needs to be downloaded and placed in the PS package. This will ensure the latest online help for the Seclore products with the latest feature explained. If the online help package is not downloaded and available, an error message is displayed. Fixed the issue where Seclore Lite for Mac installation package was downloaded on iPad after clicking on Download Seclore in the buffer file.
Before the fix: If a user does not have Seclore app for iOS installed in their iPad and opened a protected file from email, the buffer file was displayed in the browser. On clicking the Download Seclore option, Seclore Lite for Mac was downloaded instead of redirecting the user to the App store.
This was observed in the iPadOS Fixed the issue where the owner of the excluded Hot folder was not changed once the owner of the parent Hot Folder changed. Before the fix: When the owner of a parent Hot Folder was changed, the exclude Hot Folder inside the parent Hot Folder was still tagged to the previous owner. After the fix: The parent of the excluded Hot Folder changes automatically to the owner of the parent Hot Folder.
Before the fix: The alignment was affected when zoomed in or out. After the fix: The alignment is adjusted according to the screen size and resolution, and large values do not overlap or spill in the neighbouring columns.
Removed the Active Directory Operating System Version field from the AD Configuration page as it does not accept any other values apart from , and As the field is now obsolete and did not accept any other value, it has been removed from the page. Fixed the issue where the UI of the error page, stating that the browser is unsupported, was not properly displayed. Fixed the issue where when a file owner searched for a file in the Policy Server using the File ID, an error message was displayed instead of successfully displaying the file in the results.
Fixed the issue where a redistributor was able to approve access request even after the rights of the redistributor on the protected file had expired. Before the fix: When an unauthorized user requests for access to a protected file, the request is sent to the owner as well as redistributors of the file. The redistributor, with expired rights on the protected file, was able to approve such access request. This resulted in the expiration of the link for the owner and other redistributors with rights to the file.
Additionally, the requestor did not receive access to the file. After the fix: The redistributor, with expired rights on the protected file, cannot approve access request on a protected file.
An error message will be displayed instead. Fixed the issue where the user was able to see the buffer file in an Unsupported Browser with the options to either open the protected file or download the agent. Before the fix: When a user opened an HTML wrapped file in an unsupported browser, the buffer file was displayed with options to open the file in the Seclore Online Editor or to download the agent.
After clicking either of the two options, the Unsupported Browser page was displayed. After the fix: The Unsupported Browser page is displayed when a user tries to open an HTML wrapped protected file in an unsupported browser.
Seclore for O Introducing collaboration in Seclore for O You can now edit documents online and save your changes directly into SharePoint Online and OneDrive. No need to download documents anymore. This works for users external to the organisation too, if they have the required permissions.
Admins can include non-standard file formats while creating rules in the Email Auto Protector rule console. These files will be provided with full control and they will be HTML wrapped for added protection.
Mail Portal 3. Earlier, among the file sent by an external user, only a limited number of file formats were received by the internal user as protected. With this new feature, all file formats will be received by the internal user protected and HTML wrapped.
Seclore Decryption Server 3. Non-standard file formats will also be unprotected in addition to the standard file formats. PST Decryption Server 1. Server SDK 4. Before the change: When an email with attachments were protected and sent with the HTML wrap feature disabled in the Policy Server and email body protection enabled in Email Auto Protector ruled, the email was sent but with the attachments unprotected.
After the change: The email is sent in such a scenario with the email body unprotected and the attachments protected but unwrapped. Introducing support for Universal Protection where non-standard file formats will be protected using full control rights and HTML wrapped for added security.
Support for updated HTML buffer files. Starting now, the close activity for Seclore-protected files will be logged in the Policy Server. You can calculate the time a recipient has spent on a file using the feature. Time between Open and Close activities. This feature is enabled for Seclore-protected file opened in Offline mode as well. This feature must be enabled in the Policy Server, the default being disabled. Fixed the issue where Outlook stopped functioning as expected when an email group contained the ID of an ex-employee deactivated email ID.
After this fix, the email will be sent to the remaining recipients of the email group. In case the ex-employee is the only recipient of the email, a delivery failure message will be received by the sender. Fixed the issue where the cross-referencing option in a protected Word document was disabled. Updated the tooltips for file protection options in Outlook, providing precise and clear description for each Seclore option in Outlook. Fixed the issue where if a Seclore-protected PDF file is unable to open, the buffer file was displayed and on saving data loss occurred.
Before the fix: The buffer file is opened and on saving data loss occurred for the Seclore-protected PDF file. After the fix: The buffer file is opened in Read-only mode and on saving the Save-As prompt will be displayed to the user.
0コメント