www.seclore.com Sitemap

Seclore FileSecure Policy Server

 
 
				
	

Please visit this URL for all release notes from 1st July, 2020 onwards: 
http://support.seclore.com/support/discussions/11000000312

Please find release notes before 1st July, 2020 below




Release Notes for Seclore Policy Server.


Seclore 3.13.0.0
Policy Server 3.9.1.0
Jun 1, 2020

    1. Introducing a new Adminless agent for Windows. (#9173)
        a. The user has an option to download and install either Admin or Adminless mode of the new agent.
        b. Now there is no need for an IT admin to intervene while installing and operating the Adminless version for Desktop Client on Windows. 
        c. This client will provide all the capabilities that are available for the agent in the Admin mode.        
        d. Users can download both the versions of the Desktop Client from the Online Access tab of the Policy Server.
        e. The option to download both the modes of Desktop Client will be available in the Policy Server version 3.9.1.0 onwards.
        f. 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. 
        g. On updating Seclore Lite for Windows version 3.3.5.0, the Desktop Client in the Adminless mode will be installed in the system.
    2. Introducing changes in the Policy Server UI. (#9175, #9035)
        a. You can now open HTML wrapped files in Seclore Online from the Online Access tab.
        b. On the Online Access tab:
            i. Download Seclore for Windows (Adminless mode) by clicking on the Seclore for Windows or Install Desktop App link. 
            ii. Download the Seclore for Windows (Admin mode) by clicking the Admin Version link.
            iii. Download Seclore for Mac by clicking on the Seclore for Mac link (when accessed from macOS).
        c. In the Installer and Patch Management page, the tabs will now be Windows (Admin), Windows and Mac.
        d. UI improvements in Enterprise Application Section:
            i. Introduced a new Branded Enterprise Application option for ?Seclore for Microsoft 365?.
            ii. Updated the logos and subtitle text for the existing Branded Enterprise Application option. 
    3. Added ?Convert to HTML format? flag in the Hot Folder Cabinet UI in Policy Server. (#8992)
        a. The Convert to HTML format flag is added in the HolFolder Cabinet page UI.
        b. On the Policy Server UI, this flag displays if conversion to HTML wrapping for standard file formats is enabled or not in Hot Folder Enterprise Manager.
        c. If this is enabled, all standard files will be HTML wrapped on protection on placing in Hot Folder of that particular Hot Folder Cabinet.
        d. This flag can be only be updated from Hot Folder Server Enterprise Manager client. 
        e. HTML wrapping needs to be mandatorily enabled in the Policy Server Configuration page for this feature to work.
    4. Introducing changes in the User Sign Out flow in the Policy Server. (#9188)
        a. Before this change, a logged in user, on clicking sign out, was redirected to the Sign in page.
        b. Now, a logged in user, on clicking Sign out, will be redirected to the newly introduced screen.
        c. This screen will inform that the user has successfully signed out from the Seclore Policy Server.
        d. It also displays a Sign in again button.
        e. On clicking this, the user will be redirected to the Sign in screen where user can sign in again to the Policy Server.
        f. The above-mentioned flow is applicable to System Admins as well.
        g. 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.
        h. If the user is already authenticated in the SSO system, the user will be logged in automatically on clicking on Sign in again.
    5. Fixed the issue where a protected file did not open in the Online Editor if the configuration for Show Permission Badge is disabled in the Policy Server. (#9223)
    6. Fixed the issue where in certain cases an error message was displayed when an HTML wrapped file was opened in a browser. (#9208)
        a. 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.
        b. After the fix: While opening a HTML wrapped protected file in the browser, the buffer file is successfully displayed without any error.
    7. Removed Screen Capture option from the Select Activity Type filter from the Activities tab of Policy Server. (#8887)
    8. Fixed the issue where the Seclore plugin had stopped working in Outlook Web App (#9107)
        a. Before the fix: When a user clicked on the Seclore It! option while composing an email from the Outlook Web App, an error was displayed instead of the Seclore panel.
        b. Due to this error, user was unable to drag and drop documents and protect them using Seclore on OWA.
        c. After the fix: The panel opens as expected and users can successfully add and protected files before sending them using OWA. 
        d. Fix is applicable to Cloud deployments of Outlook Web Access (OWA). 
    9. 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). (#9271)
    10. 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. (#9136)
        a. 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.
        b. This was observed in certain cases.
        c. 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.
    11. Updated language support for PS messages in Spanish, French and Russian. (#9297)
    12. Updated the Policy Server Installation guide with the latest information. (#9195)
    13. System upgrades. (#8958, #8982, #8980, #8981, #8259, #9218)
    14. Other Fixes. (#9160, #9223, #9298, #9313, #9310)
 

=======================================
Seclore 3.12.1.0
Policy Server 3.9.0.0
Apr 16, 2020

    1. Enhanced the 'Download Unprotected Copy' feature to work for files opened in the read-only mode in Seclore Online Editor or if a read-only file format is opened in the Seclore Online Editor. (#9070)  
        a. The user will require Seclore Full control permissions on the file to see this option in the Seclore Online Editor.  
    2. Other fixes. (#8692, #8544, #9053) 

=======================================
Seclore 3.12.0.0
Policy Server 3.8.2.0
Apr 01, 2020

    1. Adding GDPR compliance to Seclore. (#8711) 
        a. When user logs in on the Policy Server, the ?Terms of Service? and ?Privacy Policies? will be available to the user to view. 
        b. These will inform the user of the kind of information Seclore will collect and how it will be used. 
        c. If the user agrees, they can enable the check box on the login page and proceed to login. 
    2. Introducing the capability of downloading an unprotected copy of a protected file open in the Seclore Online Editor. (#8811) 
        a. 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. 
        b. On selecting this option, the unprotected copy of the file will be downloaded. 
        c. This option will be available only if the ?Download Unprotected? flag is enabled in the Policy Server. 
        d. The user must also have Full Control on the protected file to download an unprotected copy. 
    3. Fixed the issue where error page was displayed in certain cases when the user tried to login to the Policy Server using Microsoft credentials. (#8832) 
        a. 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.
        b. After the fix: The Policy Server login page will now be displayed in the above-mentioned scenario. 
    4. Now create an enterprise application for Digital Guardian DLP Encryptor from the Custom Application option. (#8804) 
        a. Earlier, you could directly select the Digital Guarding DLP Encryptor from the Select Enterprise Application Type window. 
        b. Starting this release, you?ll have to select the Custom Application from the Select Enterprise Application Type window for creating a Digital Guarding DLP Encryptor. 
    5. Added support for Oracle 18c and 19c database versions. (#8926) 
    6. Other fixes. (#8932, #8947) 

=======================================
Seclore 3.11.1.0
Policy Server 3.8.1.0
March 01, 2020
    1) Fixed the issue where error occurred when a user changed the permission on a file protected using a new classification. (#8872)
        a) Before the change: Seclore provides five default classifications. 
        b) User can create new classifications in the Policy Server and protect files using these classifications. 
        c) When the user changed the permission on such files as mentioned in the above point, an error is displayed. 
        d) After the change: User can change permission on any protected file with any classification without any error. 
    2) Fixed the issue where the installation report displayed only a single entry for machines with same SID. (#8867) 
        a) 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.  
        b) Due to this, the installation report did not record the actual number of installations of the Seclore Desktop Client. 
        c) After the fix: The installation report will display the installation of Desktop Client in the cloned machine as a separate entry. 
        d) This will ensure that the actual number of installations of the Desktop Client is recorded in the installation report.  
    3) Fixed the issue where the direction of Arabic text in Seclore Online Viewer did not appear properly. (#8848, #8835) 
        a) Before the change: Arabic text is written from right to left unlike other languages that are written from left to right. 
        b) When a document written in Arabic and protected was opened in Seclore Online Viewer, it?s direction and orientation did not appear as expected. 
        c) After the change: The direction of Arabic will remain unchanged in Seclore Online Viewer. 
    4) Fixed the issue where disk space was getting used up when files were accessed through SharePoint. (#8781) 
        a) Before the change: When protected files were opened through SharePoint, disk space was getting used up and a warning was displayed. 
        b) This was rectified after the application was restarted. 
        c) After the change: Now user can open and work on protected files from SharePoint without encountering disk space warning messages. 
    5) Updated language support for PS messages in Spanish, French and Russian. (#8934) 
        a) Now all PS based message will be displayed in the language configured for the user. 
    6) Other fixes. (#8906, #8866) 
    

=======================================
Seclore 3.11.0.0
Policy Server 3.8.0.0
Feb 01, 2020

    1) Introducing Universal Protection for protecting any file format with sensitive enterprise information. (#8428)
        a) Earlier, a user could protect only a limited number of file formats using Right-click >> Seclore It or the ?Seclore It? button in Outlook.
        b) With this new feature, users can now protect any file format on their desktop or in Outlook.
        c) For standard file formats (i.e. MS Office, PDF, Text and Images) Advanced Protection enforces WHO (users or groups), WHAT (Read, Edit, Print etc), WHEN (date and time expiry) and WHERE (device and location).
        d) For all other formats, Universal Protection enforces WHO (users or groups), WHEN (date and time expiry) and WHERE (device and location).
        e) When an authorized recipient opens a file with Universal Protection, he/she is granted Full Control permission.
        f) The Universal Protected file opens in read-only mode and if the user edits and tries to save the file, he/she will be prompted to ?Save As?.
        g) Authorized recipients can also Unprotect these files.
        h) Universal Protection will automatically apply the HTML wrapper i.e. Sample.mp4 will be protected as Sample.mp4.html.
        i) This feature needs to be explicitly enabled on the Policy Server along with the HTML wrapping feature.
        j) 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.
    2) Introducing collaboration of MS O365 and Seclore for enhanced security of your documents on the cloud. (#8481)
        a) Now, you can edit and save your changes (if you have the required permissions) in the documents shared through SharePoint Online and OneDrive.
        b) No need to download to edit shared documents from SharePoint Online and OneDrive.
        c) External users can also edit documents if they have Edit permission from the document links shared with them.
    3) Introducing the new and improved Seclore Online Editor with enhanced UI. (#8481)
        a) The look and feel of the new Seclore Online Editor are similar to the corresponding Microsoft Office applications.
        b) Important functional buttons such as Save, Print, Undo and Redo are moved to the Only Office title bar for better visibility.
        c) In addition to the Only Office title bar, another title bar will be visible for Seclore-protected documents.
        d) 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.
        e) 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.
        f) The Edit button is not visible in the Edit mode.
        g) For non-integration workflows, documents open in the view depending on the granted permission.
        h) The download button is moved from the inside of the document to the Seclore title bar.
        i) In Read-only mode, only the option to download the Seclore agent is visible on clicking the download button.
        j) In Edit mode, the options to download the Seclore agent and to download the protected copy of the file.
    4) Now, the online help package is released separately from the Policy Server package and needs to be downloaded and placed in the PS package. (#8477)
        a) This will ensure the latest online help for the Seclore products with the latest feature explained.
        b) If the online help package is not downloaded and available, an error message is displayed.
    5) Fixed the issue where Seclore Lite for Mac installation package was downloaded on iPad after clicking on Download Seclore in the buffer file. (#8030)
        a) 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.
        b) On clicking the Download Seclore option, Seclore Lite for Mac was downloaded instead of redirecting the user to the App store.
        c) This was observed in the iPadOS 13.
        d) After the fix: The user is redirected to the App store from where they can download the Seclore Lite app for iOS or iPadOS.
    6) Fixed the issue where the owner of the excluded Hot folder was not changed once the owner of the parent Hot Folder changed. (#8420)
        a) 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.
        b) After the fix: The parent of the excluded Hot Folder changes automatically to the owner of the parent Hot Folder.
    7) Fixed the alignment of all the columns in the Activities tab, Files tab, Hot Folder Cabinets list and List Enterprise Application page. (#8167)
        a) Before the fix: The alignment was affected when zoomed in or out.
        b) In case of large Activity IDs and File IDs, the number spilled in the neighbouring column.
        c) 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.
    8) Removed the Active Directory Operating System Version field from the AD Configuration page as it does not accept any other values apart from 2000, 2003 and 2008. (#8229)
        a) As the field is now obsolete and did not accept any other value, it has been removed from the page.
    9) Fixed the issue where the UI of the error page, stating that the browser is unsupported, was not properly displayed. (#8276)
    10) 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. (#8373)
    11) 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. (#8489)
        a) 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.
        b) The redistributor, with expired rights on the protected file, was able to approve such access request.
        c) This resulted in the expiration of the link for the owner and other redistributors with rights to the file.
        d) Additionally, the requestor did not receive access to the file.
        e) After the fix: The redistributor, with expired rights on the protected file, cannot approve access request on a protected file.
        f) An error message will be displayed instead.
    12) 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. (#8280)
        a) 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.
        b) After clicking either of the two options, the Unsupported Browser page was displayed.
        c) After the fix: The Unsupported Browser page is displayed when a user tries to open an HTML wrapped protected file in an unsupported browser.
    13) Other fixes (#5806, #8323, #8269, #8231, #8270, #8687)  
=======================================
Seclore 3.10.15.0
Policy Server 3.7.6.0
December 01, 2019

    1) Providing seamless integration with Microsoft Office O365, where Seclore-protected files can be uploaded, shared and accessed (Read-Only) from Office applications like OneDrive and SharePoint using the Seclore Lite Online (Seclore Online Viewer). (#8109, #8262)
        a) Seclore now provides smooth SSO using Azure AD to access the protected files shared within teams. Users with access to document libraries can read Seclore-protected files on one-click on the filename or the Seclore button in SharePoint Online.
        b) Additionally, users can access Seclore-protected files on one click from links shared over emails in Outlook and files synced on OneDrive.
    2) Fixed the issue where the incorrect HTML wrapper file was displayed when the user tried to access an HTML wrapped file from Gmail or Apple mail in devices with iOS 13. The new and updated HTML wrapper file, with instructions to open the file, will now be visible to the users. (#8099, #8442)
    3) Fixed the issue where the three-letter word search, to search the users while protecting a file was not functioning consistently. (#8383)
    4) Fixed the issue where if there were non-ASCII characters in a file name when downloading the file from Online Editor or saving the email attachment received after editing it online, the file names were appearing incorrect with garbage characters in it. (#8031)
    5) Fixed the issue where the old and outdated error message was displayed when Policy Server URL was accessed from unsupported Operating System or browser to the user. This has been updated and now the user can see the new unsupported browsers and OS page. (#8169)
    6) Fixed the issue where the redistributor was unable to approve Request Access on Seclore-protected documents, if the file owner?s email ID is not defined. (#8103)
        a) Before the change: A user with no access encountered an error with a message stating that mail cannot be sent and hence could not access the file. Additionally, the redistributor (with Share permission on the file) was unable to provide access, encountering an error station that the link has expired.
        b) Expected behavior: At least one redistributor must be able to provide access to user requesting access, if the file owner's email is undefined and the user must be able to send a Request Access email without any error. After approval from the redistributor, the user must be able to access the file.
    7) Fixed the issue where the user was redirected to PS login page when trying to open a protected file online. Now the user will be redirected to the OAuth provider login page instead if the details are provided in open endpoint. (#8104)
    8) Other fixes. (#8110)

=======================================
Seclore 3.10.13.0
Policy Server 3.7.5.0
September 01, 2019

    1) Significantly enhanced the user experience for Agentless access of protected documents by revamping the content and behavior of the HTML pages displayed in the browser. (#7992)
        a) Enhanced the messaging and visual layout to make it more intuitive for first time users when opening protected documents directly in the browser. 
        b) Added special handling for users of the Chrome browser to open protected documents in the native app when the agent is installed.
        
    2) Improved the end user experience when downloading the Desktop Client package from the Policy Server portal. (#8032)
        a)  Before the change: On the Lite Online tab in the Policy Server portal, when the user clicks on the button to download the Desktop Client, the user was first taken to another page before the package could be downloaded.
        b)  After the change: The Desktop Client package now downloads immediately when clicking on the download button on the Lite Online tab.
    3) Removed Data Classifier option from the Enterprise Application List as it is no longer required. (#8002)
    4) Fixed the issue where Smart Sharing was not working for email IDs representing a user group. (#7922)
    5) Other fixes. (#7946 and #8042)

=======================================
Seclore 3.10.11.0
Policy Server 3.7.4.0
August 01, 2019

    1) Fixed the issue where downloading and opening a protected document from the Chrome browser?s download bar was not opening in the native application, as expected. (#7963)
        a) When the Seclore agent is installed, the user expects a protected document to open locally in the native application.
        b) Before the change: When a user downloaded an HTML-wrapped protected file in Chrome and attempts to open it directly from the download bar, it was opening in the browser, instead of opening locally in the native application. 
        c) This was happening because Google?s Chrome browser attempts to open HTML files in its own preview rather than allowing the operating system to open them. 
        d) After the change: Documents opened from the Google download bar will now be redirected to the local agent to open them directly in the native application. 
        e) Expected Behavior: For this feature to work, the Policy Server needs to be reachable and JavaScript needs to be enabled in Chrome.
        
    2) Enhanced the user experience for the Request Access approval email that is sent to the Owner and Sharer of a protected document. (#7945)
        a)  Before the fix: The Request Access approval email sent to the Owner or Sharer of a protected document shows the requester?s name only if some comments have been provided by the requester. 
        b)  If no comments are provided, there is no way for the approver to know who has submitted the request. 
        c)  After the fix: The requester?s name always appears in the approval email. 
    3) Provided the capability to extract Agent Installation details for analysis purposes, using a backend database View. (#7730) 
    4) Other fixes. (#7997, #7983, #7134)

=======================================
Seclore 3.10.9.0
Policy Server 3.7.3.0
July 01, 2019

    1) Other fixes. (#7952, #7872, #7886)

=======================================
Seclore 3.10.7.0
Policy Server 3.7.2.0
June 1, 2019

    1) Added support for multi-lingual content in the HTML Wrapper when protecting emails in the Secure Email Viewer and Outlook on the Web (OWA). (#7842) 
    2) Fixed the login issue for Hot Folder Server Admin console on Windows 2012 R2 and 8.1 with the latest March 2019 update from Microsoft. (#7880)
        a)  Before the fix: A recent Windows patch update for Windows 2012 R2 and Windows 8.1, impacted the Admin login to the Hot Folder Server Enterprise Manager.
        b)  This March 2019 Microsoft update for Windows 2012 R2 and 8.1 contained a change in the Microsoft encryption library that was used to login to the Hot Folder Server Enterprise Manager.
        c)  For more information refer to: https://support.microsoft.com/en-us/help/4489881/windows-8-1-update-kb4489881
        d)  After the fix: The changes have been made as per Microsoft recommendation and the issue is now resolved.
    3) Fixed a rare issue in the Email Auto Protector Rule Console that was preventing some Rules to be displayed in the Rule List. (#7849)
    4) Other fixes. (#7678, #7814, #7871, #7923)

=======================================
Seclore 3.10.3.0
Policy Server 3.7.1.0
April 15, 2019

    1) Enhanced the security of the password-based authentication process by increasing the minimum length of the user-defined password from 6 to 8 characters. (#7735)
        a)  Before this release: New external users created in the Seclore Identity Management system have the option of setting a password after they verify their email address at least once.
        b)  Until this release, the minimum length of the password was 6 characters.
        c)  After this release: The user-defined password must now be a minimum of 8 characters.
        d)  Other mandatory requirements of at least 1 upper-case character, 1 special character and 1 number remain unchanged.
    2) Added a new column in the Agent Installation Report to indicate if the Desktop Client is running on an obsolete version of the Windows operating system. (#7674)
        a)  Before this release: The Seclore Desktop Client now has the capability to automatically de-activate itself if the Windows operating system (OS) version is not supported by Seclore.
        b)  Microsoft periodically discontinues the support of older Windows versions and stops providing patches and security updates.
        c)  Desktops that are running such obsolete OS versions are a threat to the security of the entire enterprise.
        d)  Seclore now ensures that agents installed on very old and obsolete versions of the Windows OS are automatically de-activated.
        e)  These desktops cannot be used to open Seclore-protected documents and will not be upgraded using the standard patch upgrade mechanism of the Seclore agents.
        f)  After this release: A new column is provided in the Agent Installation Report called ?Desktop Client Discontinued Status?.
        g)  Desktops that are running on a discontinued version of the Windows OS will show the value as ?Discontinued? in this column.
    3) Fixed the issue where setting the Watermark to a blank value was not supported. (#7603)
    4) Fixed the issue where the content in the HTML Wrapper was not being displayed in the user?s language when the protected file is accessed in the Edge or Internet Explorer Browser. (#7702)
        a)  Before the fix: Users with Spanish language enabled in their Edge or Internet Explorer Browser, were seeing the English version of the content in the HTML Wrapper.
        b)  After the fix: Spanish users will now see the Spanish version of the content in the HTML Wrapper, even when accessing it from Edge or Internet Explorer.
    5) Other fixes. (#7344, #7413, #7631, #7675, #7709, #7718, #7729, #7736, #7787)

=======================================
Seclore 3.10.0.0
Policy Server 3.7.0.0
Mar 1, 2019

    1)  Provided the capability to set the default Permissions used in all the protection screens. (#7612)
        a)  Before this release, the Permissions (Read, Edit etc.) displayed by default when protecting a new email/document or adding a user to a Policy, were fixed. 
        b)  These default permissions are now configurable in the Admin console. 
        c)  While protecting a new email/document or adding a new user to a Policy, the initial Permissions displayed on the screen will be as per the Admin configuration. 
        d)  Enterprises can change these default Permissions whenever required, as per their business needs. 
        e)  Product screens that automatically display the default permissions based on the Admin configuration include: Right-click > Protect, Right-click > Change Permissions, Email Protector (?Seclore It? button in Outlook), Email Protector in Outlook on the Web (OWA) and the Policy Definition page.
        f)  Features that give Permissions automatically to users will also use these default permissions. These include: Request Access Permissions and Smart Share.         
    2)  Provided the capability to set ?Protect Body? checkbox to ?On? by default in Email Protector for Outlook. (#7612)
        a)  Before this release, the ?Protect Body? checkbox in the Email Protector for Outlook, was always Off by default. 
        b)  This default value is now configurable in the Admin console. 
        c)  By keeping this On, Enterprises can enable end users to protect the Body of their email messages with just One-click i.e. ?Seclore It?.  
    3)  Added the capability to filter out certain users when syncing users from a Windows Active Directory to the Policy Server. (#7410)
        a)  Before this release, it was not possible to filter out users when syncing user data from a Windows Active Directory (AD). 
        b)  Now it is possible to define attribute level filters to ignore users and groups when syncing them from Windows AD. 
    4)  Migrated Google Authentication from the Google+ APIs to the newly recommended Google APIs. (#7626)
        a)  Google is shutting down the Google+ service and the Google+ Authentication APIs. 
        b)  They have recommended all existing applications to migrate to their new Google APIs. 
        c)  Now onwards the Seclore Policy Server will authenticate with the recommended Google APIs. 
        d)  On-premise installations using Google Authentication will need to be re-configured to ensure they continue to function as expected. 
        e)  Cloud installations will be migrated automatically.  
        f)  Contact Seclore Support (support@seclore.com) for help on this front.    
    5)  Added multi-lingual support for the content displayed in the HTML Wrapper for any protected document. (#7555)
        a)  Before this release, the instructions displayed to a recipient for opening a Seclore-protected document in the browser, were dependent on the locale settings of the Protector.
        b)  Now onwards the instructions will be displayed based on the locale and language settings of the Recipient.   
    6)  Fixed an issue in the Rule Console for the Email Auto Protector, where the date expiry value was getting dropped from a Rule when it was being used with any language other than English. (#7666) 
    7)  Minor corrections in the Russian translation for content displayed in the end-user web portal (#7665) 
    8)  Other fixes. (#7494, #7628, #7667) 


=======================================

Seclore 3.9.5.0
Policy Server 3.6.3.0
Feb 1, 2019

    1)  Updated the Spanish language pack for Policy Server 3.6.3.0. (#7409)
    2)  Updated the Russian language pack for Policy Server 3.6.3.0. (#7475)
    3)  Other fixes. (#7391, #7479, #7495, #7557, #7587,#7588, #7599, #7600)

=======================================

Seclore 3.9.4.0
Policy Server 3.6.2.0
Jan 1, 2019

    1)  Fixed the issue where the predictive user search did not work as expected if the search results exceeded 1000 users. (#7472)
            Before the fix: The search results were not displayed - and an incorrect message was displayed instead - if the search results exceeded 1000 users. (#7472)
            After the fix: There is no maximum limit to the displayed search results. 
    2)  Other fixes. (#6839, #7420, #7442, #7446, #7471, #7474)

=======================================
Seclore 3.9.2.0
Policy Server 3.6.1.0
Dec 1, 2018

    1)  Introduced the capability to optimize the system performance for installations that have a very large number of Activities i.e. over 100 million records. (#7209)
        a)  Activity data is searchable in real-time from the web-based end user portal. 
        b)  In cases where the Activity dataset is very large i.e. upwards of 100 million records, this search performance can start deteriorating. 
        c)  A new system parameter has been introduced that can restrict the user to search for Activities in the last ?n? months only. 
        d)  E.g. if the user is restricted to search for Activity data for the last 12 months only, then the system can archiveall the Activity data prior to 12 months.
        e)  System Admins will always have access to all historical data.  
        f)  By default, this parameter is turned Off, which means the user can search for all historical data. 
        g)  This setting needs to be used carefully. 
    2)  Fixed the issue on the Policy Details page when there were a lot of users configured in the policy. (#7345) 
        a)  Before the fix: If there were a few hundred users added to a Seclore Policy, it was taking more than a few mins to load the data on the Policy Details page.
        b)  This was happening only for the owner (editor) of the Policy and not for other users who can only view the Policy. 
        c)  After the fix: Now it takes only a few seconds to load the page even if it contains a few hundred users.    
    3)  The default value of the system parameter for ?File encryption key?has been changed from AES 128 bits to AES 256 bits. (#7419) 
        a)  This has been done to strengthen overall data security and make the system even more resilient to brute force attacks. 
        b)  Older installations will continue using their existing settings only. This can always be changed in the Configuration settings page by the System Admin. 
    4)  Other fixes. (#5953, #7296, #7313, #7322, #7343, #7391)

=======================================

Seclore 3.9.0.0
Policy Server 3.6.0.0
October 16, 2018

    1) All new user experience for System Admins when defining and managing Enterprise Applications. (#7206)
        a) When adding a new Enterprise App, the user can now pick from a list of pre-defined connectors that are available out-of-the box.
        b) The option to define a custom connector is available as well.
        c) The user interface has been completely redesigned with significantly improved interactions and a new-age look and feel.
    2) Added a new pre-defined enterprise connector for the new Email Auto Protector component that protects enterprise emails automatically based on admin configured rules. (#7133)
        a) This specific connector comes with an all new Rule definition interface for protecting enterprise emails on the central email server.
        b) Each Rule that has a Filter and an Action, and the System Admin can define a sequence of these Rules.
        c) The Filter that can be based on email Sender, Recipient, Subject or X-header. The Action can be either Protect, Unprotect or Do Nothing.
        d) If an email satisfies the Rule Filter, the Action will be taken as specified in the Rule.
        e) Filters can also be defined on X-headers (XML tags) that are inserted by DLP content inspection tools. This can be used to automatically Seclore-protect emails that DLP has identified as sensitive.
    3) Added all new configuration screens in the System Admin console for defining and maintaining Policy Server configurations. (#7122)
        a) Server configurations which were earlier in an XML file, are now available in a simple and intuitive web page.
        b) Default values are pre-populated and help instructions are available at the field level, as well.
        c) System Admins can now administer remotely without needing access to the server desktop.
        d) This helps to reduce the IT overheads for deployment and maintenance of the Policy Server infrastructure, especially for multi-instance deployments.
    4) Added a new configuration screen in the System Admin console for managing agent installers and upgrade patches. (#7193)
        a) Installers and upgrade patches which had to be placed in a folder on the server, can now be uploaded in the web-based screen.
        b) A simple drag and drop interface makes it very easy and intuitive for System Admins to keep agents consistently upgraded to the latest versions.
        c) This helps to reduce the overheads of continuously deploying patches and upgrades, especially for multi-instance deployments.
    5) Fixed the issue in the Online Editor where comments in the document content inserted by a user were not showing the user?s name. (#7147)
        a) Before the fix: When a user was inserting comments in the document content, the name of the user was being displayed as ?Anonymous?.
        b) After the fix: The correct name of the logged in user will now be displayed in the comments inserted in the document content.
    6) System Admins can now define a Repository Name of up to 100 characters instead of the earlier 25 characters only. (#7153)
    7) Removed the invalid error messages showing in the backend Policy Server logs when only one custom user repository was configured. (#7176)
    8) Other fixes. (#7179, #7202, #7207, #7210, #7216, #7240, #7275, #7279, #7301, #7306)


=======================================
Seclore 3.8.2.0
Policy Server 3.5.1.0
August 16, 2018

    1) All new calendar control with improved visual design and better aesthetics. (#7123)
    2) Fixed the issue where some internal users were wrongly redirected to the external user login page if their email ID had some upper-case characters. (#7142)
        a) When the user enters an email ID on the login page, it is compared with a list of internal domains to identify the user as an internal user. If the email ID matches any domain in the list, the user is taken to the internal user login page, else redirected to the external user login page.
        b) Before the fix: If the user entered an email ID with upper case characters (i.e. your.name@YourCompany.com) it wouldn?t match a configured domain (i.e. @yourcompany.com), because the text comparison was case-sensitive. 
        c)  After the fix: This text comparison is now case insensitive, and user is redirected to the correct login page. 
    3) Other fixes. (#6373, #6611, #7125, #7128, #7143)

    
=======================================
Seclore 3.8.0.0
Policy Server 3.5.0.0
July 1, 2018

    1) Upgraded the Online Editor with a few enhancements and fixes to improve the stability and compatibility with Microsoft Office formats. (#6807)
        a) Documents will now load and open much faster than before ? almost 30% faster. 
        b) Company logo is now displayed in the loading screen that appears before the document editor is displayed in the browser. 
        c) Company logo in the About page was not being displayed on mobile devices. This is now fixed. 
        d) Comments in Word, Excel and PowerPoint documents were earlier getting dropped if the user edited and saved the document in the Online Editor. These are now preserved even after the document is edited and saved (downloaded). 
        e) Expected behavior: Comments in older Word formats (.doc) will not be displayed as of now. 
        f) Earlier, Excel formulas that referenced other Excel documents were getting dropped if the document was edited and saved in the Online Editor. This is now fixed.
        g) Earlier, hyperlinks to other files were broken if the document was edited and saved. This is now fixed. 
        h) Earlier, text with strike through formatting was displayed without the strike through. This is now fixed. 
            i) Expected Behavior: Pivot tables in Excel files cannot be manipulated in the Online Editor. However, the Pivot table will be unaffected even if the document is edited and saved in the Online Editor. If the downloaded file is opened in Excel, it will work as expected in the native Excel application. 
    2) Added support for the new ?Smart Sharing? feature added to Email Protector in Outlook for Windows and Mac agents and for Agentless Access in the browser. (#6789) 
    3) Users no longer need a Protector license for Sharing (Redistributing) protected emails and documents. (#6811)  
        a) Earlier, every user needed a Protector license to use the ?Share? permission. 
        b) Removing this requirement will allow even external users to Share documents and emails more freely with those who really need access.
        c) Now Sharers (Redistributors) can approve Requests for Access even without having a protector license. 
        d) However, only File Owner and internal Sharers (Redistributors) will get approval emails when end users initiate a Request for Access. (#6808)   
    4) Enhanced the Request Access feature to give Read and Edit permissions by default when approving the request. (#6817)
        a) This will make information access easier for the requester without the approver having to do anything additional.
        b) The approver can always choose to modify the permissions given at any time.
    5) Enhanced the Request Access feature to send approval emails to users that are part of a group that has Share permissions. (#6917) 
        a) Earlier, if a group was given Share permissions, the Request Access approval email was not being sent to the users in the group. 
        b) Now, the users in the group will be sent the email and any one of them can approve the Request for Access.
        c) To minimize email overload, only a maximum of 10 users in the group will be sent the approval email.  
    6) Enhanced the Revoke Access feature in the Outlook Email Protector to allow revoking access for any user on the protected attachments. (#6894) 
        a) Earlier, if the email and attachments were protected using the Seclore It button in Outlook, the user could Revoke Access for the email recipients only. 
        b) However, if the document was shared with other users that were not in the email recipient list, they could not be revoked from the same screen. 
        c) Now all users who have access to the protected email or attachments will be displayed in the list and can be revoked. 
    7) Enhanced the Email Protector for Outlook on the web to include HTML wrapping for all protected documents. (#6825)
    8) Added server-side enhancements to support the new Android features. (#6925)
        a) Opening protected emails and attachments that are HTML wrapped directly in the Android app. 
        b) Improved messaging to help new users to install the app and open a protected file for the first time.   
        c) Extending the Online Editor to allow users to edit protected documents in the app.
        d) Extending the Secure Email Viewer to allow users to Reply to protected emails within the app itself. 
    9) Enhanced the Daily Activity Summary and Unauthorized Activity Alert emails to include the user?s email ID against each activity in the list to make it more intuitive than before. (#6283)
        a) Before the change: In the Daily Activity Summary email that File Owners receive every day, only the name of the user who performed the activity was mentioned. 
        b) Even in the Unauthorized Activity Alert email, only the user?s name was displayed. 
        c) After the change: Now email ID will also be displayed against each activity in these reports.    
    10) Fixed the issue where Request Access approval emails were not being sent in a specific case to the File Owner. (#6938)
        a) Before the fix: If an unregistered user opens a protected document for the very first time and authenticates using Google login, the approval email was not being sent to the File Owner.
        b) After the fix: The File Owner will now receive the approval email, as expected.   
    11) Fixed some text editing issues in the Secure Email Viewer that is used to View and Reply to protected email messages in the browser without any agent. (#6898, #6899)
    12) Changed the Buffer content in the protected email body to say ?This is a protected email? in place of the earlier message - ?This is a protected document?. (#6924) 
    13) Fixed the issue where in certain cases, the Sharers (Redistributors) were not receiving the Request Access approval emails. (#6906) 
        a) Before the fix: If the Request for Access was generated by an internal user that was part of a Windows Active Directory repository, the Sharers were not receiving the approval email. 
        b) After the fix: Sharers will always get the approval email in all cases. 
    14) Reduced the different messages displayed when opening a file in the Online Editor to just one to make it simpler and more intuitive to the end user. (#6942)    
    15) Fixed the issue that occurs only in a specific case when a new user is being registered automatically during the document protection process. (#5839) 
        a) Before the fix: When a document with ampersand (&) in its name is being protected and a new unregistered user is given permission on the document, the Protector sees an error ? ?Failed to register the user??.
        b) After the fix: The user gets successfully registered, as expected.  
    16) Updated the Spanish language translations for all features up to this current version i.e. Policy Server 3.5.0.0 (Seclore 3.8). (#6828, #6998)
    17) Fixed the issue where a blank page was displayed in the Lite Online Editor when opening documents from a Document Management System (e.g. SharePoint). (#6997)
    19) Other fixes. (#6781, #6801, #6810, #6865, #6869, #6888, #6893, #6902, #6905, #6908, #6926, #6927, #6929, #6941, #6966, #6967, #6991, #7007, #7008)

    
=======================================
Seclore 3.7.0.0
Policy Server 3.4.0.0
April 15, 2018
    
    1) Significantly enhanced the capabilities of the Online Editor when it is integrated with an enterprise application. (#6377, #6460)
        a) Users can now invoke a protected document from the enterprise application directly in the Online Editor, then edit it and save the changes back into the enterprise application.
        b) Additional integration interfaces are now available to allow and integrated enterprise application to get back the updated version of the edited document from the Online Editor.  
        c) This allows the users of the integrated application to collaborate on sensitive enterprise content without requiring an agent to be installed. 
    2) Enhanced the predictive search capabilities when protecting a document or searching for users in the web portal etc. (#6587)
        a) When adding permissions to a document when the user starts typing a recipient?s name or email id, the system searches and displays the matching users below the search box. 
        b) Earlier all active and inactive users in the Seclore Policy Server were being displayed in this list. 
        c) Now, only ?active users? in the user repository (Windows Active Directory, Seclore Identity Management or custom repository) will be displayed. 
        d) This will ensure that no currently inactive users will be assigned new permissions.  
        e) However, in the Policy Server portal, when searching for users, both active and inactive users will be displayed, since auditing and tracking is required for all users.
        f) It is now possible to append multiple fields from the underlying user repository into the Seclore user name field e.g. ?Name?, ?Designation? and ?Department Name? can be concatenated into the Seclore ?Name? field, so that a user?s name in Seclore will appear as ?John Doe Vice President Finance?.        
        g) Searching is much faster and richer than before. User can search for any string token in the email id e.g. john.doe@acmegroup.com will be listed if the user searches for either of these: ?john?, ?doe?, ?acme?, ?acmegroup? etc.   
    3) Restored an earlier feature that allowed a user to mark a File as ?Inactive? from the Policy Server web portal. (#6614)
        a) File Owners and OU Admins can mark a file as ?Inactive? or ?Active?.  
        b) Inactive Files cannot be accessed by anyone including the File Owner. 
    4) Added the capability for an OU Admin to view File permissions from the Policy Server web portal. (#6619)
        a) OU Admins can search for Files in the web portal and click on the key icon to view the Recipient Permissions and Policies for a File. 
    5) Enhancements to simplify the user experience for Bulk Actions in the Policy Server web portal and make it easier. (#6620)
        a) Transferring ownership of Inactive Files, which was not allowed earlier.  
        b) Transferring ownership to a new File Owner who doesn?t have a Protector license, which was not allowed earlier. 
        c) A warning message is displayed to the user if the new File Owner is an external user. 
        d) Revoking access of a user that is deleted in the underlying repository or is in an unmapped repository. 
    6) Fixed the issue where CSV files were not being sent via email after editing them in the Online Editor. (#6710)
    7) Fixed the issue in the Online Editor where the system response was much slower than expected when editing a file in the iOS app. (#6707)
    8) Fixed the issue where a document would not open in the Online Editor from a mobile device, if the agent download link in the Online Editor is hidden (via Policy Server configuration). (#6755) 
    9) Fixed the issue where some OU Admins were unable to access File and Activity data in the Policy Server web portal when a Windows AD with some specific configuration was integrated with Seclore. (#6717)
        a) Before the fix: This issue occurred only when the Seclore Policy Server was integrated with a Windows AD that was setup as a forest with a parent domain and multiple child domains.
        b) In this scenario, the OU Admin mapped to the child domain was unable to access File and Activity data in the Policy Server web portal. 
        c) After the fix: The OU Admin mapped to the child domain is now able to access all File and Activity data as expected.  
    10) Updated the Spanish language translations for all features up to Policy Server 3.3.1.0. (#6752, #6771) 
    11) Other fixes. (#5928, #6600, #6612, #6680, #6716, #6769, #6744, #6767, #6775)


=======================================
Seclore 3.6.2.0
Policy Server 3.3.1.0
Mar 16, 2018

    1)  Added a new feature called ?Replace User? to allow one user?s permissions to be transferred to another by the current File Owner or OU Admin. (#6319)
          a)In the Policy Server web portal under the Files menu, in the Actions drop down, a new option called ?Replace User? is now available. 
          b)The user can search and select multiple files and click on ?Replace User? to start this operation.
          c)Select the current user who needs to be replaced and the new user who will take his/her place and proceed further. 
          d)On completion of this process, all permissions given directly on the Files to the earlier user will be dropped and same permissions will be added for the new user. 
          e)Any permissions given to the earlier user via Hot Folders or Policies will remain unchanged. The File Owner or OU Admin will need to modify those Policies or Hot Folders individually. 
          f)If user permissions are federated from an external enterprise application, those permissions will need to be modified within that application itself. 
    2)  Added a new feature called ?Replicate User? to allow one user?s permissions to be replicated to another by the current File Owner or OU Admin. (#6395)
          a)In the Policy Server web portal under the Files menu, in the Actions drop down, a new option called ?Replicate User? is now available. 
          b)The user can search and select multiple files and click on ?Replicate User? to start this operation.
          c)Select the current user who needs to be replicated and the new userand proceed further.  
          d)On completion of this process, all permissions given directly on the Files to the current user will be replicated and added as permissions for the new user. 
          e)Any permissions given to the current user via Hot Folders or Policies will also be replicated and added as permissions for the new user directly on the Files. 
          f)If user permissions are federated from an external enterprise application, those permissions will need to be modified within that application itself.           
    3)  Enhanced the Secure Email Viewer to allow users to Reply to protected email messages within the browser itself. (#6322) 
          a)This will enable users to Reply to protected email messages directly from a web browser and will also enable users on mobile devices as well. 
    4)  Added support for opening files in the Online Editor from integrated enterprise applications within an iframe. (#6465)  
    5)  Simplified the email ID verification process by changing the alphanumeric Security Code (One Time Password ? OTP) to a completely numeric code. (#6461)
          a)The 6-digit numeric security code is much easier for end users to read and key in, especially on mobile devices. 
    6)  Enhancements to enable a better mobile experience when users are opening protected documents or email messages on iOS   and Android devices. (#6347, #6463) 
    7)  Enhanced the Request Access screens to be more mobile friendly. (#6462)
    8)  Fixed the issue in the Outlook Email Protector where an unexpected error was displayed if the Track or Revoke pages were refreshed. (#6379)
    9)  Fixed the issue in the Outlook Email Protector where clicking on the ?View in browser? link from the Track page was not applying the date filter as expected. (#6381)
          a)Before the fix: All activities for all files in the protected email were being displayed. 
          b)After the fix: The default filter of ?last 7 days? will be applied to show only the latest activities in the list.    
    10) Fixed the page refresh issue on the Security Code (One Time Password ? OTP) entry page. (#6595)
          a)Before the fix: Whenever the page was refreshed, another email was sent to the user unnecessarily. 
    b)  After the fix: Email is only sent once and is not affected by page refresh.     
    11) Fixed some minor UI and icon issues on the Revoke Access bulk action page. (#6382)
    12) Other fixes. (#6331, #6386, #6536, #6591, #6617)


========================================
Seclore 3.6.0.0
Policy Server 3.3.0.0
Feb 1, 2018

  

    1) Enhanced the Right-click > Seclore It! protection screen with additional capabilities under the ?More? column on the main screen. (#6164) 
        a) Allow the user to select granular permissions (Copy Data, Offline, Screen Capture etc.) when protecting a file.  
        b) Users now have the option to set expiry as a specific ?date? or ?number of days? from file opening.    
        c) Also allow the user to specify location restrictions using ?lock to device? or specifying an ?IP address range?.
    2) Added a feature called Revoke Access to allow a user?s permissions on a file to be removed by the current File Owner or OU Admin. (#6107) 
        a) This feature is available in the File Search screen under ?Actions? in the Policy Server console.  
        b) The user can revoke access on multiple files at a time.  
        c) Only individual permissions assigned directly on the files can be revoked. 
        d) This feature cannot be used to revoke permissions assigned via a Policy or Hot Folder. The Policy or Hot Folder needs to be modified separately.  
        e) This feature cannot be used to revoke permissions assigned via integration with any other enterprise system. The Policy will need to be modified or in the case of Policy federation, the permissions in the underlying system will need to be changed.
        f) Revoke operations will be tracked in the Admin Audit Log with request type as ?Revoke File Access?. 
    3) Enhanced the Admin Audit logging for Transfer Ownership operations. (#6107)
        a) Earlier when transferring ownership of multiple files, a new Audit Log entry was recorded for every File. 
        b) Now it will log one entry each Transfer Ownership operation that includes all the files in that operation.
        c) The new log entries will show under request type as ?Transfer File Ownership? and the older entries will show under ?Transfer File Ownership (Old)?.      
    4) System Admin user can now modify Hot Folder configurations even after they are deleted from the Hot Folder Enterprise manager. (#5485)
        a) This is required in certain cases, when a Hot Folder is not required to protect new files and has been deleted from the Hot Folder Enterprise Manager console. 
        b) Files protected earlier with that Hot Folder may still be active, so the System Admin may need to change the Policy or Owner of the deleted Hot Folder.   
    5) Added support for printing protected documents directly from the Online Editor. (#6030, #6226)
        a) The Print permission control will be enforced in the Online Editor.  
        b) User having print permission on a protected file will be allowed to print it directly to a local printer. 
        c) The printout will also have the same watermark that is displayed on the screen. 
        d) Expected behavior: The user can print to a virtual printer that generates a PDF output. Each page in the PDF output will be a watermarked image, so the user cannot copy any written content out as text. 
    6) Significantly enhanced the watermark displayed on a protected document in the Seclore Online Editor and Online Viewer. (#6287)
        a) The watermark is now displayed multiple times across the document, so that it covers all the content.   
        b) It is also much less intrusive and doesn?t interfere with the readability of the content. 
    7) Added the Seclore badge on a protected document when it is opened in the Seclore Online Editor. (#6244) 
        a) The badge appears in the lower right corner of the window and clicking on it displays the user's permissions and the name of the File Owner.
    8) Added support for deploying the Seclore Online Editor in a high availability configuration.
        a) Multiple instances of the Online Editor can be hosted behind a common load balancer. 
        b) This provides higher resiliency and better performance under heavier workloads.
        c) Requires: A hardware or software load balancer that supports session stickiness. It is recommended to use a hardware load balancer to reduce the risk of service failure.        
    9) Fixed the language issue in the email received by a user after editing a document in the Seclore Online Editor. (#5787)
        a) Before this fix: Even though the user?s locale (browser settings) was set to Spanish, the email with the edited version of the document was received in English. 
        b) After the fix: A Spanish user will always receive a Spanish email only.
    10) Fixed the issue in the Online Editor where an agent download link was displayed even when the user?s operating system was not supported by a Seclore agent. (#5910, #6236)
        a) Before this fix: In the top right corner of the main screen a hyperlink called - ?Open this document on your device? was always displayed.
        b) On clicking this link, the system auto detects the user?s operating system and downloads the agent compatible to that OS. 
        c) On an unsupported operating system, the user could download but could not proceed any further.   
        d) After this fix: This link will not be displayed if the user?s operating system is not supported by a Seclore agent.
    11) Fixed the issue in the View Permissions screen in the Policy Server where the UI was getting distorted in Internet Explorer 9 (IE 9). (#6232)
        a) Known behavior: For now, the user will be given a suitable message that this page is not supported on IE 9 and he should upgrade to a higher version of the browser.    
    12) Added server-side support for new features to be released in the next version of the Outlook Email Protector ? ?Track?, ?Revoke? and ?View Online?. (#6234, #6285)
    13) Other fixes. (#5717, #6191, #6162, #6192, #6223, #6241, #6242, #6254, #6255, #6263)    

========================================
Seclore 3.5.0.0
Policy Server 3.2.0.0
Dec 1, 2017

    
    
    1) Added support for Windows Server 2016 (for Policy Server and Lite Online Server) and SQL Server 2016. (#6117) 
    2) Updated the Policy Server to support latest versions of Java and Tomcat. (#5951)
        a) Java 8 update 144
        b) Tomcat 8.5.23
    3) Added the License type (Production, POC, or UAT) on the License Summary page on the Policy Server portal for OU Administrators and System Administrators. (#6102)
    4) Provided the File Owner the ability to revoke or change permissions granted by Sharers (users with ?Share? permission). (#6140)
    5) Added the option to switch off access request emails sent to the Sharer (user with ?Share? permission). (#6167)
        a) This feature will be enabled by default 
        b) The option is applicable at the server level i.e. it will be applicable for ALL documents protected by that Policy Server
    6) Fixed the issue where no suitable error message was displayed on the Seclore login page when Javascript was disabled in the browser. Now a suitable error will be displayed in such cases.  (#6182) 
    7) Updated nomenclature to reflect new Seclore terminology. (#6103)
        a) ?Redistribute? to ?Share? 
        b) ?Credential? to ?Policy?
        c) ?FileSecure? to ?Seclore?
    8) Added the ability to configure different document size upload limits for different file formats in Seclore Lite Online. Previously, the same size limit applied to all formats. (#6186)
    9) Updated the Spanish language support for all features up to Policy Server version 3.1.0.0. (#6126)
    10) Other fixes. (#5810, #5947, #5876, #6108, #6110, #6111, #6118, #6165, #6166, #6168)

========================================
FileSecure 3.4.0.0
FileSecure Policy Server 3.1.0.0
Nov 1, 2017


    
    1) Introduced the new Seclore Online Editor that allows users to open, edit and save protected files directly in the browser without any agent. (GA Release)
        a) Documents will be displayed in a rich editor that gives the user a very native application like experience for Word, Excel, PowerPoint and PDF documents.
        b) A dynamic watermark will be displayed as usual.
        c) Users with edit permission can edit and save the modified file on their local computer.
        d) After the file is closed in the browser, the user will receive the last saved copy on email.
        e) Formats supported: Office (docx, doc, xlsx, xls, ppt, pptx), pdf and text (csv, rtf and txt).
        f) Expected Behavior: Older Office formats (doc, xls, ppt) will open in read-only mode without the editing capability.
    2) Enhanced the user experience of the login module for end users. (#5789)
        a) The user starts by entering only an email ID and gets automatically redirected to the specific login page that is relevant for him.
        b) Enterprise (typically Windows AD) users will be prompted to enter Enterprise user ID and password. 
        c) New users registered in Seclore?s identity management system can login using a simple One-Time Password (OTP) that is auto-generated and sent to their registered email ID. 
        d) Seclore-managed users can choose to continue with the OTP based authentication or setup a password and use that to login every time. 
        e) Enhanced security for Seclore-managed users by forcing an email ID verification every 60 days.   
    3) Improved user experience for File and Activity Search to help users search and analyze information about their protected files. (#5849)
        a) All new UI that is more intuitive, more contextual with better aesthetics and shows only information that is most important and relevant.
        b) File and Activity search is much easier and faster with a completely revamped frontend and backend for better real-time tracking. 
    4) Fixed the issue where an email ID with single quotes (?) could not be registered or authenticated successfully. (#5854)
        a) Before the fix: An email ID with a single quote (e.g. john.mc?donald@example.com) could not be registered in the Seclore Identity Management system.  
        b) In cases where a 3rd party identity management system was integrated with Seclore, users with single quotes in their email ID were not able to login successfully.  
        c) After the fix: Email IDs with single quotes can be successfully registered and authenticated.  
    5) Other fixes. (#5622, #5867, #5884, #5903)

========================================
FileSecure 3.1.0.0
FileSecure Policy Server 3.0.1.0
Aug 16, 2017

  
    
    1) Added support for opening files in Seclore Lite Online from integrated third-party applications (e.g. SharePoint) in the same browser tab in an iframe. (#5718)
        a) Earlier, all such files used to open in a new tab. 
        b) This behavior is configurable: organizations can choose whether such files will open in the same tab or a new tab.
    2) Fixed the issue where the Seclore file summary screen (invoked by clicking right click > View File Details) displayed that the user had Full Control permission even though it was only partially available. (#5775)
        a) The ?Full Control? permission comprises of Screen Capture, Macro, and Unprotect permissions. Earlier, the screen displayed a green check mark against Full Control even when one or two of the above were not available to the user. 
    3) Other fixes. (#5208, #5569, #5608, #5637, #5638, #5682, #5708, #5742, #5779, #5781, #5793)
    
========================================
FileSecure 3.0.0.0
FileSecure Policy Server 3.0.0.0
June 16, 2017

    
    
    1) Completely re-imagined user onboarding process to make it just 1 step for new external users opening their first file. (#5428)
        a) When a user protects an email attachment using the ?Seclore It!? button in Outlook on Windows or Outlook on the web, the file gets protected and then wrapped in an HTML layer. 
        b) The HTML wrapper is added to the protected file only if at least 1 one external user is found in the email recipient list. 
        c) External users can open their first protected file in just 1 step by verifying their email ID or using their Google login. 
        d) The protected file opens online in the browser without any agent installation or file upload. 
        e) If the agent is already installed when the file is opened, the HTML wrapper is automatically removed and the protected file opens in the native application as usual.
        f) Formats supported: Office (docx, doc, xlsx, xls, ppt, pptx), pdf and text (rtf and txt)
    2) Changes to reduce end user friction that were no longer required after HTML wrapper is available for onboarding new users. (#5588)
        a) Dropped the new user invite email that was leading the user to the Start page. 
        b) Dropped the link to the Start page in the Welcome email that is sent to a new user after setting the password.    
    3) Introduced the new Seclore Online Editor that allows users to open, edit and save protected files directly in the browser without any agent. (Beta Version) (#5535)
        a) Documents will be displayed in a rich editor that gives the user a very native application like experience for Word, Excel, PowerPoint and PDF documents. 
        b) A dynamic watermark will be displayed as usual. 
        c) Users with edit permission can edit and save the modified file on their local computer. 
        d) After the file is closed in the browser, the user will receive the last saved copy on email.  
        e) Formats supported: Office (docx, doc, xlsx, xls, ppt, pptx), pdf and text (csv, rtf and txt).    
        f) Expected Behavior: Older Office formats (doc, xls, ppt) will open in read-only mode without the editing capability.  
    4) All new Email Protector for Outlook on the web to protect email attachments sent from the Office 365 web-based email interface. (#5484)
        a) The Seclore add-in allows users to drag and drop attachments that need to be protected directly in the Outlook web interface. 
        b) Supported file extensions will automatically get wrapped in HTML if the recipient list contains an external user. 
        c) Any new users in the recipient list are automatically registered. 
        d) This feature also supports on-premise installations of Microsoft Exchange Server 2016.
        e) Expected Behavior: Protecting the email body is not available as of now. 
    5) Automatic login to Policy Server when user is logged in to the Seclore agent on the same computer. (#5546)
        a) When the Policy Server URL is invoked in the browser, the user?s agent login will be used to automatically login to the Policy Server as well. 
        b) File Owners can now experience the ease of getting things done with just 1 click. E.g. Clicking on the button in the Request Access email to approve a user?s request, clicking on the hyperlink in the Daily Activity Summary email to see the complete activity list etc.   
    6) All new Admin dashboard feature to allow OU Admin users to monitor and track protected files. (#5479)
        a) Allows OU Admins to monitor and track protected files from anywhere using a single web-based console. 
        b) Aggregates and monthly trends displayed for 6 different metrics: ?Unauthorized Activities?, ?High Risk Activities?, ?Files Protected?, ?Active Protectors?, ?Active Users? and ?Authorized Activities?.
    7) Updated the Spanish language support for all features up to Policy Server version 2.59.0.0. (#5581)
    8) Corrected the Spanish translation of an error message displayed in the Request Access feature. This message is displayed when the File Owner is attempting to approve a request and the system identifies it as an invalid operation. (#5585)
    
    
========================================
FileSecure 2.109.0.0
FileSecure Policy Server 2.59.0.0
May 15, 2017

   
    
    1) Improved the Request Access feature by sending access request emails to users with ?Share? permissions (up to 10 users per file) in addition to the File Owner. (#5433)
    2) Enhanced Seclore location-based access controls to allow the addition of a maximum of 1000 IP address ranges, up from 10 earlier. (#5525)
    3) Updated the default Seclore logo that appears on the Policy Server portal and login pages. (#5531)
    4) Resolved the issue in which users would get an error while protecting an email in Microsoft Outlook 2016 if they were prompted to log in manually. This issue would not occur if they were already logged into the Seclore agent before protecting the email. (#5514)
    5) Other fixes. (#5529, #5536, #5438, #5545, #5481, #5482)

========================================
FileSecure 2.108.0.0
FileSecure Policy Server 2.58.0.0
April 1, 2017

   
    
    1) Improved the login process for users common to more than one user repository. Such users will no longer need to select the desired repository while logging in. Now when they log in in the context of a particular file, their repository will be selected automatically. (#5160)
    2) Added the feature to capture basic usage statistics to improve the software usability and performance. (#5176)
    3) Introduced page scrolling in the UI when a user opens a file online in the browser. (#5335)
    4) Allowed integrated enterprise applications to combine Policy Federation with pre-defined policies created in Seclore. Most commonly used to give external users created in Seclore access to Enterprise document repositories. (#5228)
    5) Added the requirement to give consent before upgrading to this version of the Policy Server. (#5358)
    6) Updated Spanish language support for all features up to and including Policy Server version 2.57. (#5255)
    7) Fixed the rare issue where a licensed user trying to classify a file got an invalid error message stating that a classification license could not be assigned. (#5405)   
    8) Other fixes. (#3875, #5050, #5212, #5326, #5333, #5359, #5368, #5407, #5409, #5412, #5434, #5225, #5376)

========================================
FileSecure 2.106.0.0
FileSecure Policy Server 2.57.0.0
Feb 01, 2017

    
    
     1) Enhanced the user experience of the File Protector (Right-click > Protect) screen by improving the autocomplete behaviour for user search. (#5102)
     2) Other fixes. (#5112, #5164)
     
========================================
FileSecure 2.105.0.0
FileSecure Policy Server 2.56.0.0
Jan 16, 2017

    
    
     1) Significantly enhanced the new user experience for opening protected files in the browser using the Start page. (#5080,#5092) 
         a) Removed the need for pop ups to be enabled in the browser for opening the document in the Lite Online window.   
         b) Added the capability of opening up to 3 documents at a time in the same browser window. 
         c) Allowing the user to switch between multiple open documents using Windows-like buttons: Minimize, Restore and Maximize.  
         d) Enhanced the visual appeal of the document display window along with a few new capabilities to view 'First Page', 'Last Page' and 'Fit to Screen'.
         e) Provided the agent download link within the Lite Online window for users who want to open the document on their local device. 
         f) Expected Behaviour: For obsolete browsers like Internet Explorer 6 and 7, the older version of the window will be displayed which requires pop-ups to be enabled.     
     2) Further simplified the user experience for opening a protected file in the browser by dropping the ?Set Password? screen. (#5114)
     3) Added the Request Access feature for opening protected files in the browser. (#5113)
         a) Automatic registration of new users along with the access request.
         b) Real-time email notifications sent to the File Owner with the requester?s details and comments.
         c) One-click Approval or Decline options provided within the email notification itself.
         d) Easier and dynamic permission assignment even after the information is shared.
     4) Fixed the issue where protected files were not opening online in Mozilla Firefox when using the private browsing mode. (#5163)  
     5) Updated Spanish language support for all features up to Policy Server version 2.55. (#5105)
     6) Other fixes. (#5084, #5089, #5094, #5097, #5111, #5124, #5156)

========================================
FileSecure 2.102.0.0
FileSecure Policy Server 2.55.0.0
Dec 1, 2016

    Features:
    
     1) Added support for authenticating users with their Google account. (#4974) 
         a) New users can sign-up with their existing Gmail ID and password. 
         b) Policy Server single sign-on: users already logged in to Google in the same browser will be logged in to Policy Server automatically.  
         c) Easier user on-boarding and file access without the need to remember another password.    
     2) Added support for macOS 10.12 Sierra. (#5068)
     3) Added support for iOS 10. (#4970)
     4) Optimized the querying of user groups from Windows Active Directory. (#5019)  
        
    Bug Fixes:
    
     1) Issue: Minor language corrections in the user on boarding emails in Spanish. (#5016)
        Resolution: Fixed this issue. 
     2) Other fixes. (#4881, #4902, #4981, #4997, #5018)  

    Expected Behavior:
    
     1) Signing in using a mobile phone (using Google?s ?Use your phone to sign in? feature) is not supported on Internet Explorer 9 and below.  
    
========================================
FileSecure 2.100.0.0
FileSecure Policy Server 2.54.0.0
Oct 01, 2016
    
   Features: 
    
    1) Improved the backend performance and reliability of the user identity management module by replacing the existing LDAP repository with OpenDJ. (#4876)
    2) Introduced ?One Time Login? configuration for a user repository which is enabled by default to allow end users to stay logged in even after a system restart. (#4903)
    
   Bug Fixes:     
   
    1) Issue: Configuration Validator in the System Admin console did not verify the PDF Buffer file properly from the database. (#4753)
       Resolution: Fixed this issue. If there is a configuration error, the ?Server restart required? message is also displayed. 
    2) Issue: In the System Admin console on the Enterprise Application page, the navigation to the Policy Federation tab did not work properly. (#4879)
       Resolution: Fixed this issue.
    3) Issue: Minor language corrections required for email Activity Alerts in Spanish. (#4900)
       Resolution: Fixed this issue. 
    4) Other fixes. (#4584, #4777, #4829, #4882, #4915, #4967)  
    
========================================
FileSecure 2.98.0.0
FileSecure Policy Server 2.53.0.0
Sept 01, 2016

   Features:
    
    1) Improved the new user on boarding module to make it simpler and more intuitive. (#4826)
        a)All new Start page with options to view a protected file in the browser itself or download the agent to open the file locally.   
        b)First time users can open a protected file in the Online Viewer without account activation i.e. without setting a password.
        c)Completely redesigned the New User Invitation email and made it more intuitive. 
        d)New users now receive a Welcome email after account activation i.e. setting a password. 
    2) Enhanced the Agent Installation Report (for System Admin) by adding ?Agent Type? as a separate column. (#4747)     

========================================
FileSecure 2.97.0.0
FileSecure Policy Server 2.52.0.0
Aug 15, 2016

   Features:
    
    1) Introducing BYOK (Bring Your Own Key) with support for Hardware Security Module (HSM) to make backend security for the database even more tamper-proof and enterprise-controlled. (#4742)
    2) Added support for AES 256-bit encryption for protected file content. (#4867)   

   Bug Fixes: 

    1) Other fixes. (#4836)

========================================
FileSecure 2.96.0.0
FileSecure Policy Server 2.51.0.0
Jul 28, 2016

   Features:
    
    1) Enhanced security between Policy Server and an integrated application with an additional encryption layer controlled entirely by the enterprise. (#4660)
    2) Strengthened internal product security for client-server communication with an additional encryption layer within the SSL tunnel. (#4664)
    3) Enabled integrated applications to be assigned certain advanced privileges - such as unprotecting all files protected by that Policy Server. (#4662)
    4) Added support for High Availability (HA) configuration for Lite Online Server. (#4670)
   
   Bug Fixes:
    
    1) Other fixes. (#4440, #4492, #4696, #4749)    

========================================
FileSecure 2.93.0.0
FileSecure Policy Server 2.50.0.0
Jun 1, 2016

Feature:
    1) Seclore Lite Online now supports image file formats. (#4644) 
        a) bmp
        b) png
        c) tiff/tif
        d) jpg/jpeg
        e) gif
    
Expected Behavior:
    1) Transparent areas in gif and png images will be displayed in white.
    
    2) Transparent areas in tiff/tif images will be displayed in black.
    
==========================================================================================================
FileSecure 2.92.0.0
FileSecure Policy Server 2.49.0.0
Apr 30, 2016

Features and Enhancements:
    1) All new web-based user interface to manage Hot Folder configurations centrally without having access to the computer where the Hot Folder Server is deployed. (#4491)
        a) Once Cabinets and Hot Folders are defined on the actual server via the Enterprise Manager, all further changes can be done from this web interface on the Policy Server.
        b) This provides a centralized console to make changes to any Hot Folder across all the servers deployed in an organization.
        c) Name, Classification, Owner and Policies can be changed for any Hot Folder in the enterprise.
    
    2) End user?s language preferences are automatically detected and updated in the user?s profile on the Policy Server. Users can now receive emails in their preferred language e.g. Activity Alerts in Spanish or German. (#4596)  
    
    3) Removed the need to restart Policy Server when the System Administrator makes configuration changes to User Repositories and Classifications. (#4588)   
    Note: Any changes made in Repository configuration are reflected after 5 mins in all instances of Policy Server, in case Policy Server is running in load-balancing mode. In case you want to change any critical Repository configuration like server name, username, password, domain name etc., it is recommended that you shut down all instances of Policy Server except one, make changes in Repository configuration and start all instances of Policy Server to ensure changes are reflected immediately.
    
    4) Updated Online Help for all features released until Mar 2016 (#4279, #4593)
    
Bug Fixes:
    1) Issue: Minor UI flaw on the protected file display screen in Seclore Lite Online. (#4570)
    Resolution: Fixed this issue.   
    
    2) Issue: Close button in certain error pages did not close the page. (#4569)
    Resolution: Fixed this issue.
    
    3) Issue: Inconsistency in the error message displayed when syncing repositories. (#4585)
    Resolution: Fixed this issue.    
    
    4) Other fixes: (#4590, #4591)

==========================================================================================================
FileSecure 2.89.0.0
FileSecure Policy Server 2.48.1.0
Mar 15, 2016

Enhancements:
    1. Upgraded to latest versions of Java and Tomcat. (#4466)
        a. Java 8 update 66 (1.8.0_66)
        b. Tomcat 8.0.32
        
    2. Enhanced the SMTP validation email in the ?Config Validator? component to include the following details: (#4462)
        a. Policy Server URL and version
        b. Seclore product version
        
    3. Enabled automatic assignment of protector licenses when a user shares (redistributes) a protected file with someone else. (#4494) 

    4. Removed the need to restart the Policy Server when adding or updating an Enterprise Application with Policy Federation. (#3799)  

    5. Updated Spanish language support for all features up to Policy Server version 2.47.0.0. (#4495)

Bug Fixes:
    1. Issue: On the new ?File Protector? and ?Change Permission? screens, new user registration failed if the email address entered had either a leading or trailing space. (#4527)
    Resolution: Fixed this issue.   

    2. Issue: Minor language mistake in the German error message displayed on the New ?Set Password? page in the ?Forgot Password? process. (#4490) 
    Resolution: Fixed this issue. 

    3. Other fixes: (#2276, #4460, #4489)
        
==========================================================================================================
FileSecure 2.88.0.0
FileSecure Policy Server 2.48.0.0
Feb 15, 2016

Features: 
    1. Richer enterprise application integration with federation of File Owner and Classification. (#4403) 
        a. Policy Federation now allows the File Owner and Classification to be federated in real time from the integrated application - each time the file is opened. 
        b. File Owner and Classification picked up from the integrated application are also saved in the Seclore Policy Server for reporting purposes. 

    2. Enabled automatic user creation in Seclore for users who already have access to the file in the integrated application. (#4403) 

    3. More parameters sent to the integrated application in the Policy Federation request: (#4444) 
        a. Agent ID and name
        b. Requesting IP address
        c. File status: active or inactive
        d. File Protector: ID, name and email address 
        e. Protection type: Basic or Advanced
        f. Protection time
        g. Time of first access by the current user

Bug Fixes: 
    1. Issue : The watermark from the integrated application was not being displayed if the file was opened by the File Owner. (#4403) 
    Resolution : Fixed this issue. The federated watermark will be displayed for File Owners too. 

    2. Issue : Some Policy Server images were not properly displayed in Internet Explorer when the Apache webserver was hardened with specific parameters. (#4346)  
    Resolution : Fixed this issue. 

Expected Behaviour: 
    1. If the real-time values for File Owner and Classification are unavailable or invalid, the last available values in the Seclore Policy Server will be used.  

    2. Files protected by the integrated application using Policy Federation cannot be protected with Policies defined in the Seclore Policy Server ? to ensure that Policies are managed in one system only.   
        
==========================================================================================================
FileSecure 2.85.0.0
FileSecure Policy Server 2.47.0.0
Jan 7, 2016

Features:
    1. Email activity alerts sent to file owners for activities performed on their files. (#4257)
        a. Real-time email alerts for unauthorized activities
        b. Daily summary for all activities of the previous day

    2. All time values displayed in the user's time zone ? regardless of the server time. (#4257)

    3. The 'Request Access' feature is now available for the FileSecure Desktop Client. (#4407)
    
Bug Fixes:
    1. Issue : When two users have the same name, it is difficult to distinguish between them on the File Protector and File Permissions screens. (#4402)
    Resolution : Email addresses of recipients displayed as a tooltip in the new File Protector and File Permissions screens.
        
==========================================================================================================
FileSecure 2.83.1.0
FileSecure Policy Server 2.46.1.0
Dec 1, 2015

Bug Fixes:
    1. Issue : FileSecure WebConnect API integration does not work with FileSecure 2.83.0.0. (#4347)
    Resolution : Policy Server has been updated to resolve this.
        
==========================================================================================================
FileSecure 2.83.0.0
FileSecure Policy Server 2.46.0.0
Nov 30, 2015

Features:
    1. All new 'Change Permissions' user interface that is simpler and more powerful. (#4238)
        a) Individual recipients can be added to a protected file i.e. without including them in a policy.
        b) Automatic user onboarding of new recipients using their email address. 
        c) Simple and intuitive interface for novice users while still providing advanced features for power users.       
          
    2. Added a new 'Configuration Validator' feature to verify the Seclore Policy Server installation status. (#4275)
        a) Logging in as a System Admin will display a new Home tab with the current status of the important configuration parameters.
        b) Appropriate error, warning or success messages are displayed for each parameter.
        c) For each error message a 'Recommended Action' is provided to resolve it.

    3. Enhanced the File Protector user interface for the Mac agent. (#4255)
        a) Enabled the 'Share' (Redistribute) permission to be given to individual Recipients.
        b) Enabled the protection of a file with an existing Policy.

    4. Support Microsoft SQL Server 2014 and Oracle 12c Database Server.(#4340)
         
Bug Fixes:
    1. Issue : Differences between the Desktop Client and FileSecure Lite for Windows shown on WebConnect Page in Policy Server Portal. (#4271)
    Resolution : Policy Server has been updated to resolve this.
        
    2. Others (#4256, #4292)
        
==========================================================================================================
FileSecure 2.81.0.0
FileSecure Policy Server 2.45.0.0
Oct 10, 2015

Features:
    1. All new 'Auto Assign License' feature that assigns protector licenses on demand. (#4177)
        a. Removes the need to assign licenses manually and helps lower IT Admin overhead.
        b. Allows free 'overuse' of purchased licenses to help discover the license needs for the enterprise.  
        c. Speeds up product awareness and adoption to reduce overall enterprise risk due to data leakage.
        d. Allows the overuse limits to be reset or extended as part of the license regularization process. 
        e. Weekly email notifications to keep IT stakeholders well informed about current license status.
        f. On-demand reports available with daily tracking of license assignments.

Bug Fixes:
    1. Issue : Policy Server does not allow download of FileSecure client installers from latest operating systems like Windows 10, Android 6, iOS 9 and MAC 10.11. (#4253) 
    Resolution : Policy Server has been changed to resolve this.
        
    2. Others (#4155)
    
==========================================================================================================
FileSecure 2.79.0.0
FileSecure Policy Server 2.44.0.0
Aug 14, 2015
  
Features:
    1. Support for protecting files on FileSecure Lite for Mac. (#4020)
        a. Easy and intuitive user interface for protecting files using FileSecure Lite for Mac.
        b. Protection options are available on right click of file/folder.
        c. New external users are registered automatically.
        d. Supports all the FileSecure supported formats.
        e. Requires FileSecure Lite for Mac 1.3.0.0 or higher.
        f. Internet Explorer versions 7 and below are not supported for this feature.
            
    2. Updated language packs for Spanish and German. (#4090, #4091, #4092)

    3. Others (#4019, #4095, #4096, #4121, #4122)
        
Known behaviour:
    1. While adding recipients in FileSecure Lite(Windows) during file protection, sometimes entries get repeated more than once. It will be observed only when the protection feature is enabled in FileSecure Lite(Windows) and Internet Explorer 8 is installed on the machine.
        
==========================================================================================================
FileSecure 2.77.0.0
FileSecure Policy Server 2.43.0.0
July 17, 2015
  
Features:
    1. All new Request Access module that allows users to request for access on a file. (#3953) 
    More details as listed below - 
        a. Automatic registration of new users along with the access request.
        b. Real-time email notifications sent to the File Owner with the requester?s details and comments.
        c. One-click Approval or Decline options provided within the email notification itself.
        d. Easier and dynamic permission assignment even after the information is shared.
        e. Requires FileSecure Lite for Windows 1.7.0.0 or higher.
        Known Issue:
        a. Currently FileSecure does not enable request access on files which have external Policy federation.
        
    2. Others : #4031
        
==========================================================================================================
FileSecure 2.75.2.0
FileSecure Policy Server 2.42.1.0
June 12, 2015
  
Bug Fixes:
    1. Issue : In some remote cases, during user on-boarding, the user is unable to confirm registration (#3988).
    Resolution : Policy Server has been changed to resolve this.

    2. Issue : In some remote cases, user is unable to open certain files using FileSecure Lite for Windows and Android (#4010).    
    Resolution : Policy Server has been changed to resolve this.

    3. Others : #4011, #4012

==========================================================================================================
FileSecure 2.75.0.0
FileSecure Policy Server 2.42.0.0
May 8, 2015
        
Features:
    1. Support for formatting options like font and colour in watermark configuration. (#1933)
        a. Watermark configuration would allow for formatting options for font, font style (bold/italic) and colour. This option is also available when watermark details are received from Access Right Adaptor.
        b. FileSecure Lite Online (WebConnect) has been enabled to consume the watermark formatting configuration and render the document.

    2. End User Help Manual is available in Spanish. (#3819)  

Bug Fixes:
    1. Issue : Fonts are not cached on the browser leading to delay of rendering of pages in some cases.(#3824)
    Resolution : Policy Server has been changed to cache the fonts. Fonts would be cached for 30 days by default.

    2. Others : #2853, #3840, #3847, #3848

==========================================================================================================
FileSecure 2.74.0.0
FileSecure Policy Server 2.41.0.0
Apr 17, 2015

Features:
    1. FileSecure Policy Server now supports Java 8 and Tomcat 8. (#3800)
        a) Java 8 support starts with JDK 1.8.0_40 and Tomcat 8.0.20. 
        b) To support Java 8, existing installations on Windows Server 2003 need to be migrated to 2008 or above. 
        c) New installations will be supported on Windows Server 2008 onwards only. 
        d) It is highly recommended to migrate existing installations on Tomcat 7 to Tomcat 8 at the earliest.
        e) Java 7 and Tomcat 7 support will be available for a limited period. 

    2. Authentication mechanism for Enterprise Application Integration (ARA). (#3745)  
        a) Policy Server can now authenticate with a username and password (HTTP basic authentication mechanism) to fetch access permissions from an external Enterprise Application.

    3. Enabled Policy Server to fetch details of watermark from external Enterprise Application (ARA). (#3748) 
        a) An external Enterprise Application can now send the watermark content along with the access permissions to the Policy Server. 
        b) This watermark is displayed when a document is opened in FileSecure Lite.
        c) In case the watermark is not sent by the Enterprise Application, Policy Server uses its own configured watermark. 

    4. Enabled user on-boarding for FileSecure Lite for Mac. (#3827)

    5. Updated language packs for Spanish, German and Russian. (#3797, #3706, #2829)

Bug fixes:
    1. Issue : System Administrator user was unable to switch from Enterprise Application navigation link back to the System Administrator page. User was required to re-login to achieve the same.(#3798)
    Resolution : Additional links are now available on Policy Server to switch back to System Administrator page smoothly.

    2. Issue : Password policy not displayed properly while creating an instance of Enterprise Application. Also help link on the same page was not working as expected. (#3833, #3042)
    Resolution : Policy Server has been updated to take care of these issue. Help link is no longer available on the page.
        
    3. Issue : Unable to fetch details of the user on the HotFolder definition page when owner of the HotFolder is deleted from Simple Active Directory. (#3785)
    Resolution : Policy Server has been updated to take care of this issue.
        
    4. Issue : Link to download Desktop Client on WebConnect page redirects to the "Verify" link of Download WebWizard instead of the "Install" link in some cases.(#3826)
    Resolution : Policy Server has been updated to take care of this issue.
        
    5. Others : #3752 
        
==========================================================================================================
FileSecure 2.72.0.0
FileSecure Policy Server 2.40.0.0
Feb 27, 2015

Features:
    1. A completely new user onboarding module that simplifies the onboarding process, with highlights as mentioned below (#3704, #3773)- 

        a. Completely new user interface that is both friendly and functional for the first-time user experiencing FileSecure.
        b. Simplified and intuitive process flow that is now reduced to just 2 steps ? set password and agent installation (self-service).
        c. All screens are built to be desktop and mobile friendly.
        d. Auto-detecting the user?s platform to provide instructions and installers that are platform specific.
        e. Wide variety of platform support including Windows and Mac computers, Apple and Android mobile devices.
        f. User onboarding is now a self-service process that will accelerate the initial adoption of the system.

        Note: It is strongly recommended to also upgrade FileSecure Lite for Windows and FileSecure Identify Management(FIM) along with this release to have a complete and smooth experience of this onboarding module.
    
    2. Other Issues: (#3718, #3774)
    
==========================================================================================================
FileSecure 2.69.0.0
FileSecure Policy Server 2.39.0.0
Dec 10, 2014

Features:
    1. Support for Web Service based integration with FileSecure WebConnect. (#3587)
        a. Any Enterprise Application can now invoke this Policy Server Web Service to display a protected file in the Web Browser.  
        b. The end user can click on a link in the source application and view the file in the Web Browser without any software installed. 
        c. Once the technology integration is established, this becomes the easiest way for an end user to view a protected file that resides in another Enterprise Application. 
        d. The end user experience is seamless and uniform across all platforms ? Computers, mobile devices, etc. 

        Note: 
        i. Details about the Web Service API enabled to achieve the above, is available as a separate document. 
        ii. As part of this feature, the close button which was earlier available while viewing the file in WebConnect has been removed.

    2. Added Spanish language support in the Policy Server. (#3626)
        
    3. Others Issues: (#3629)
        
==========================================================================================================        
FileSecure 2.67.0.0
FileSecure Policy Server 2.38.0.0
Nov 24, 2014

Features:
    1. Introduced Enterprise Application Integration Interface.(#3492, #3598)
        a. Significantly enhanced the integration capability of FileSecure by allowing to inherit the access permissions from another Enterprise Application. 
        b. If an Enterprise Application like a DMS, ERP or Reporting tool is integrated with FileSecure to protect downloaded files, it is now possible to enforce the access permissions of the Enterprise Application on the FileSecure protected file.
        c. Any changes in the user permissions in the Enterprise Application will be automatically applied on the downloaded files.
        d. This requires a technology integration with the Enterprise Application. This is possible by building an Access Rights Adaptor (ARA) for each such integration with Enterprise Application. 
        e. A default ARA is shipped as part of this release. This adaptor is capable of communicating with an Enterprise Application over http/https and fetch user permissions for a given protected file. It has XML based communication protocol to talk to the Enterprise Application. More details on the same is available as part of the integration documentation.

        Limitations/Known behaviors:
            a. Restart of the Policy Server is required if any detail for the above integration is changed in Policy Server. 
            b. From this release onwards, user is prohibited to detach a file from its Hot Folder. This means that once a file is protected by Hot Folder it will always remain protected with the credentials of the Hot Folder. Additionally, more credentials can be applied to the file.

     * A complete developer guide is available to know more details about the technology integration with the Enterprise Application.

    2. Introduction of NEW Web Services to allow creation and search of user within Repositories. (#3604)
       Currently, FileSecure Policy Server exposes a set of Web Services that can be used to integrate with third party systems like DMS. These Web Services include authentication of user, creating/updating HotFolders, protect/unprotect files etc.. To further enhance integration capability of FileSecure, Web Service APIs have been added/updated as follows:
            a. Allow user creation in FIM (FileSecure Identity Management) repository. Target repository can be configured on the Policy Server.
            b. User search has been enabled across repositories, through email address. Email address passed as input to the web service is expected to be of a user only and not a group.
         
    3. Enhanced the SIEM integration capability to allow querying for file activity logs by using the external file reference. E.g. If a file is protected on download from a DMS (Document Management System), it is now possible to query for FileSecure activity logs using the file reference id in the DMS. (#3609)
     
Bug Fixes: 
    1. Issue: While defining credential, user is unable to select credential if redirected from Email Secure Send or HotFolder definition UI page on Policy Server. This issue is only observed with Internet Explorer 11. (#3572)
    Resolution: Policy Server has been updated to take care of this issue.
    
    2. Others Issues: #3596
        
==========================================================================================================
FileSecure 2.64.2.0
FileSecure Policy Server 2.37.2.0
Sep 24, 2014

Bug Fixes: 
    1. Issue: Microsoft Office documents with various objects like chart, organizational chart are not rendered properly in WebConnect. In addition to this viewing documents in WebConnect has performance issues. (#3491)
        Resolution: WebConnect is updated to take care of this issue.
    2. Issue: The deployment of WebConnect is restricted to 32-bit Tomcat. (#3491)
        Resolution: WebConnect is updated to take care of this issue. Now WebConnect can be deployed on 32 bit as well as 64 bit Tomcat. It is recommended to deploy WebConnect on 64 bit Tomcat on high end hardware, for better performance.
    3. Issue: Viewing of CSV document in WebConnect is not supported. (#3491)
        Resolution: WebConnect and Policy Server are updated to allow user to upload CSV documents in WebConnect. Only comma (,) separated CSV documents are supported.
    4. Others Issues: #3515
        
Limitations/Known behaviours:
    1. JDK/JRE 1.7 update 25 onwards is required by WebConnect. If Converter is deployed on Java 1.7 update 21 then PPT/PPTX files having 'calibri' font will not be rendered properly in WebConnect.
    2. For some PDF documents, WebConnect will not able to render the text highlighted using Adobe Reader.
    3. In Excel formats, if there are large number of columns then it might be possible that some columns are not rendered properly while viewing the document in WebConnect.
    4. Please refer Known limitations behaviours document for more details. 
 
==========================================================================================================
FileSecure 2.63.0.0
FileSecure Policy Server 2.37.1.0
July 15, 2014
    
Bug Fixes:
    1. Issue: Policy Server stores redundant data related to User machine in database which results in performance degradation and storage shortage. User's machine details are captured by Policy Server client like Desktop Client or FileSecure Lite (Windows) whenever User performs any File Activity like Protect or Unprotect and sends to Policy Server. Policy Sever extracts relevant information like Machine Name, IP Address from it and stores it in database and also stores complete machine details in database. Complete machine details is redundant as relevant information is already stored in database separately and it causes performance degradation and storage shortage. (#3390)
        Resolution: FileSecure Policy Server has been changed to not store complete machine details as relevant information is already stored separately. 
    2. Issue : There is no provision to download the FileSecure Lite (Windows) installer from Policy Server. (#3388)
        Resolution: 
            a. User can download FileSecure Lite (Windows) from WebConnect page. 
            b. User is redirected to new page where he/she can download FileSecure Lite (Windows) or FileSecure Desktop Client if he/she accesses Start URL (https:\\\start) from Buffer File on platforms supported by Desktop Client or FileSecure Lite (Windows) and Policy Server is deployed without WebConnect.
            c. User is redirected to error page where he/she can download FileSecure Lite (Windows) if he/she accesses Start URL (https:\\\start) from Buffer File on platforms not supported by Desktop Client or FileSecure Lite and Policy Server is deployed without WebConnect.  
    3. Issue: Certain labels are shown in English for German Users. (#3398)
        Resolution: FileSecure Policy Sever has been changed to display these labels in German.
    4. Issue: Help and Forgot Password link are not right aligned on Login page. Also, Help, Refresh Captcha and Cancel link not right aligned on Reset Password page. (#3297, #3306)
        Resolution: FileSecure Policy Server has been changed to align UI properly on Login and Reset Password page.
    5. Issue: A file with an apostrophe (') in its name does not open in WebConnect. (#3305)
        Resolution: Policy Server has been updated to take care of this issue.
    6. Issue: Javascript error is shown on Login page if Policy Server is configured with repositories other than Active Directory or LDAP (Repositories which requires only username and password for authentication). (#3318)
        Resolution: FileSecure Policy Server has been changed to take care of this issue.
    7. Issue: Incorrect error message is displayed in FileSecure Lite (Android) when file larger than maximum file size is opened in FileSecure Lite (Android). Maximum file size can be configured in Policy Server. (#3307)
        Resolution: Policy Server has been updated to take care of this issue.
    8. Issue: Incorrect error message is displayed in WebConnect when file larger than maximum file size is uploaded in WebConnect. Maximum file size can be configured in Policy Server. (#3294)
        Resolution: Policy Server has been updated to take care of this issue.
    9. Other Issues: #3374, #3392, #3387
    
Limitations/Known behaviours:
    1. Help manuals are not updated for the changes made in this release.
    2. In Internet Explorer 9, if 'Do not save encrypted pages to disk' is enabled, FileSecure Lite (Windows) Installer can not be downloaded from any of the FileSecure Lite (Windows) download links provided.
    3. Browser scroll bar does not work when Desktop Client and FileSecure Lite (Windows) comparison (Compare Versions) page is open in Chrome or Opera.
    4. Database migration to this release from any previous Policy Server version may take longer than usual if the database is too large.

==========================================================================================================
FileSecure 2.60.0.0
FileSecure Policy Server 2.37.0.0
May 23, 2014

Features: 
    1. Enhanced user experience by providing common login page across all user repositories in Policy Server. (#3008)
        As a part of Seclore FileSecure global objective of continuous improvement of the user experience, authentication page of Policy Server has been enhanced to simplify the login process for the end user.
        Prior to this release, before providing authentication details, user was required to select correct user repository to authenticate. This was an extra step that user was required to perform in order to get authenticated, with a high probability that the user might not know which repository to select for authentication. In such a case, users end up providing right credentials in the wrong user repository, resulting in failure of authentication and user getting confused!
        To solve the above problem, Policy Server now provides a common login page for authentication, where in user just needs to enter the login-id and password. Policy Server intelligently identifies and authenticates the user in correct user repository. In case Policy Server finds the user in more then one repository, user is prompted to identify correct user repository. 
        However, there are some cases where repository implementations are little complex e.g. Single Sign On (SSO) repositories, customer specific or third party repositories. In such cases Policy Server is unable to authenticate the user automatically and user would still be required to select the correct repository.
        
        To access System repository, there is a separate URL as "https://://sysadmin"

        The 'Forgot Password' link is visible to all end users when at least one FIM repository is configured on the Policy Server. However user from only FIM repository will be able to reset the password.
            
    2. Optimization for searching users and groups in repositories by providing 'starts with' operator. (#3193)
        Currently, the Search Entity feature for each repository in Policy Server searches the users and groups by providing 'contains' operator for each LDAP search query.
        To make search filter more fast and optimized, a new configuration 'Search Operator Type' is added to each repository instance. Using this configuration, Policy Server can be configured to search the Users and Groups using either the 'contains' or the 'starts with' operators. The default operator is 'contains'.
        This means that users and groups can be searched for either by checking whether actual user or group name  ?contains? the search keyword, or whether the user of group name ?starts with? the search keyword.

    3. German language update for Policy Server. (#3197)
        German language support is provided for the features/bug fixes introduced till Policy Server version 2.35.0.0. 

    4. New fixes and features in FileSecure Documentation.
        FileSecure user and administrator documentation has been updated with this release. Major changes include changes to reflect the following - 
            a. New login page for End Users and System Administrators
            b. The HotFolder Analyser report
            c. The new FileSecure buffer file

Bug Fixes:
    1. Issue: While login into FIM Repository, an incorrect error message "Could not login - Authentication failed: password has expired. Please contact administrator.(-304026)" is displayed if user enters incorrect login credentials - even though the password of user has not really expired. (#2534, #1594)
        Resolution: Policy Server is updated to show correct error messages if invalid credential is provided while login.
      
    2. Issue: While accessing the link in buffer file from Android 2.3.x device, the user is not redirected to FileSecure Lite (Android) page at the Google Play Store. Also link to FileSecure Lite (Android) is not visible on the WebConnect page when accessed from Android 2.3.x device.(#3172)
        Resolution: Policy Server has been updated to take care of this issue.
    
    3. Issue: FileSecure Lite (iOS) displays an error while viewing protected files if the time display settings are configured in the 12-hour format. (#3202)
        Resolution: Policy Server has been updated to take care of this issue.
    
    4. Other Issues: #3167, #3194, #3285
    
Limitations/Known behaviours:
    1. The authentication process will be same from all the clients and browsers (including from desktop or mobile) but the user interface may vary a little based on the following factors - 
        a. Browser and its version, especially in HTML4 and HTML5 supported browsers.  HTML5 browser gives enhanced and faster user interface as compared to HTML4 browser. 
        b. Standard and Compatibility modes of the browser. 
        c. Desktop machine and mobile devices.
        
    2. Once a user authenticates successfully in a SSO enabled repository from a browser, no other user is allowed to log into any other Repository from that browser unless the browser cookies are cleared. Please read the aiding document detailing the way information is cached using cookies in case of user authentication.
     
==========================================================================================================
FileSecure 2.57.0.0
FileSecure Policy Server 2.36.0.0
Mar 14, 2014

Features: 
    1. FileSecure Lite (Android) support. (#3095)
        Policy Server has been changed to support newly released FileSecure Lite. For more information about FileSecure Lite, Please visit https://play.google.com/store/apps/details?id=com.seclore.filesecure.android.lite 
        Also, link to download the same is shown on WebConnect page.
        Note: To view non-PDF file formats in FileSecure Lite, Policy Server requires an additional component - WebConnect to be deployed. Minimum version of WebConnect component required is 1.3.0.0, which has been released as part of this Policy Server. Both components - FileSecure Policy Server and WebConnect need to be updated simultaneously. Updating one without updating the other is not recommended and may result in unexpected behaviour. 
         
    2. Introduction of Drag and Drop feature on WebConnect UI. (#2856)
        Currently to view a file in WebConnect, the user has to select the protected file by using the browser specific mechanism for selecting files. As part of the Policy Server UI enhancement, user is allowed to drag and drop file(s) on WebConnect page to view in WebConnect. User can now drag and drop files directly from his/her machine and drop them into the 'Drag and Drop' box provided. Additionally, the user can use old mechanism of selecting file to view in WebConnect.
        Note: The Drag and Drop feature is not implemented for browsers which does not support HTML5 for e.g. all versions below Internet Explorer 10. These browsers will continue to show the browser specific control for selecting the file.
        Also, User experience is enhanced by processing the uploaded file immediately as against the current implementation where the user has to click on the 'View' button to start the actual processing of the file. Only one file will be processed at a time. 

    3. New fixes and features in the Help Manual. (#3096)
        FileSecure help manuals have been updated with the following new fixes and features.
            a. Introduction of 'Lite Viewer' access right.
            b. Manual is updated to include help for different roles in FileSecure.
    
Bug Fixes:
    1. Issue: Policy Server does not display the client download link on WebConnect for Windows 8. (#3121)
        Resolution: Policy Server is updated to allow downloading the FileSecure Desktop Client on Windows 8.
        Known Behaviour:
            Link to download Desktop Client is shown to user on WebConnect page on following Operating System even though they are not supported:
                a. Windows Server 2012
                b. Windows 8 (32 bit)
                c. Windows 8.1 (32 bit)
            At the time of installation, Desktop Client will throw error for the unsupported Operating Systems.
    
    2. Issue: Option to download File Activity report is unavailable in case search result exceeds the configured limit of search result. (#3122)
        Resolution: A download button is provided in the File Activity module when the searched records exceed the configured limit.
    
    3. Issue: Java Script error shown on login page of Policy Server, if the Java Script debugger is active. (#3123)
        Resolution: Policy Server has been updated to take care of this issue.
    
    4. Other Issues: #3124

Limitations:
    1. Restart of Policy Server application from Tomcat Manager may lead to unexpected behaviour. It is recommended to restart Tomcat Server itself to achieve the same.

==========================================================================================================
FileSecure 2.56.0.0
FileSecure Policy Server 2.35.0.0
Feb 25, 2014

Features : 
    1. Introduction of NEW access right 'Lite Viewer' for WebConnect & FileSecure Lite. (#3032)
        Currently to view FileSecure protected file in WebConnect or FileSecure Lite (iOS) the user is required to have 'Screen Capture' access right. These viewers show watermarked protected file, hence even if the screen is captured, watermark (typically having username and timestamp) is present on the protected file. ?Screen Capture? right as a side effect also allows the user to capture screen of the file through FileSecure Desktop Client, where the document does not have a watermark. The owner of file actually ONLY wants to allow the user to view the file using WebConnect or FileSecure Lite but the user also gains the right to take a non watermarked screen capture of the file. This is concerning from security perspective and hence the a new access right ? ?Lite Viewer? has been introduced in this Policy Server release.
          
        Going forward to view protected documents in WebConnect or FileSecure Lite the user would require 'Lite Viewer' right only. If user has only 'Screen Capture' rights, viewing in WebConnect or FileSecure Lite is not allowed. 'Screen Capture' right would be required to allow Print Screen through Desktop Client, to view protected files in Virtual Machines or through Remote Desktop Sharing etc. 'Lite Viewer' and 'Screen Capture' rights will be independent of each other. 
        
        As part of the Policy Server migration process, all the existing Credentials with 'Screen Capture' right would be updated to also provide 'Lite Viewer' right to the users in the Credential. This is to done to maintain backward compatibility.
        
    2. Introduction of NEW Web Services to allow HotFolder Cabinet User to create Predefined Credential. (#3035)
        Currently, FileSecure Policy Server exposes a set of Web Services that can be used to integrate with third party systems like DMS. These Web Services include authentication of user, creating/updating HotFolders, protect/unprotect files etc. To further enhance integration capability of FileSecure, Web Service APIs have been added/updated as follows:
          a. Allow creation/updation of Predefined Credential by HotFolder Cabinet User.
          b. Mapping users/groups to Predefined Credentials, so that they these can actually get attached to a HotFolder.
          
    3. Enhanced Desktop Client installation report. (#3023) 
        FileSecure Policy Server provides a report wherein System Administrator can identify the machines on which FileSecure Desktop Client is installed along with other details like version, IP address, machine name etc. To make this report complete and more informative, following enhancements have been done: 
            a. A new column "Last Detection Time" is added, which indicates the last time when Desktop Client from that particular machine contacted Policy Server and updated details.
            b. A new column "FileSecure Current Version" is added, which indicates current FileSecure version of Desktop Client.
            ** In some cases this column may be blank since this information is only available in Desktop Client versions above 2.37.0.0.
            c. Columns have been rearranged in the order of importance. 
        
    4. Enhanced the File Activity module for better user experience. (#3034)
        All the pages in File Activity module are displayed with new improved stylesheet (CSS).
        
    5. Support for MSSQL Server 2012. (#3052)
        From this release onwards, support for MSSQL Server 2012 has been enabled.  
     
    6. Support for Windows Server 2012 (64-bit) for FileSecure Server components. (#3053)
        From this release onwards, FileSecure Server components - Policy Server and WebConnect module have been enabled to be deployed on machines with Windows Server 2012 operating system.
        
Note: The Desktop Client version 2.36.1.0 is deprecated.
        
=============================================================================================================================
FileSecure 2.55.0.0
FileSecure Policy Server 2.34.0.0
Jan 6, 2014

Features : 
    1. Improved External User Management. (#2166)
        FileSecure Policy Server and FileSecure Identity Management (FIM) are being integrated into a single component. FIM functionality will be incorporated into the FileSecure Policy Server itself. This initiative is part of Seclore?s continuing efforts to improve external user onboarding and management for FileSecure customers. With this change, internal users can register their external collaborators (vendors, partners, external consultants, freelancers etc.) themselves from the Policy Server portal. No self-registration is required by external users. Hence, the burden of selected FileSecure activities on external parties can be significantly reduced. 
       
        This option is only enabled for users of the repository which is mapped to the FIM based repository. A new tab "User Info" will be visible to these users now to achieve the same. New user which is being created and the requester user both will be intimated via mail once the new user is approved by the FIM admin. Apart from this, there is an option to create pre-approved users of FIM based repository, which do not require FIM admin approval. This is again a configurable parameter at the repository level. Option to change or reset password of the FIM user is available on Policy Server itself. User is not required to access FIM application to do so anymore. Please refer to FileSecure IRM documentation for further details.

        Note: Both components ? FileSecure Policy Server and FIM ? need to be updated simultaneously for this change to take effect. Updating one without updating the other is not recommended and may result in unexpected behaviour.

    2. Transferring File Ownership for Deleted Users. (#1625)
        Prior to this release, the ownership of a file could not be transferred to another user if the original owner had been deleted from the repository (such as the Windows Active Directory or FIM.). This release includes a new feature in FileSecure IRM that enables OU Administrators to search for deleted users in the Policy Server cache. 
        OU Administrators can use FileSecure?s search functionality to display all files owned/protected by a deleted user whose details are still stored in the Policy Server cache. Please refer to FileSecure IRM documentation for further details. 
        
        Note: The functionality to search for deleted users is available to OU Administrators only. 

    3. Enhanced Web Services API for protection to allow protection of file, using HotFolder Id and external File Id. (#2855) 
        Every HotFolder in a Policy Server is assigned a unique number (known as the HotFolder Identifier or the HotFolder Id) by FileSecure. This is also referred to as the internal Id of the HotFolder. A third-party application integrating with FileSecure IRM may map another Id to the FileSecure HotFolder ? known as the external HotFolder Id. This external HotFolder Id is typically a unique Identifier in third-party applications e.g. GUID of Document Library in SharePoint. 
        Until now, only the external HotFolder Id (along with the external file Id) could be used by third-party applications to protect files. From this release, third-party applications can protect files using internal HotFolder Id and external File Id as well. In case both (external and internal) HotFolder Ids are provided, then external HotFolder is takes preference. 

    4. Faster File Activity Search. (#2974)
        FileSecure database schema has been upgraded in order to improve the performance of file activity searches. The database performance while loading file activity search results will improve as compared to previous versions.

    5. New Product Documentation. (#2841)
        This release includes two new user guides - 
            FileSecure IRM HotFolder Administrator Guide: This guide explains the HotFolder component of FileSecure IRM and is meant for HotFolder administrators.
            FileSecure IRM System Administrator Guide: This guide explains the administrative features of FileSecure IRM and is meant for System Administrators.
    
Bug Fixes :
    1. Issue : Policy Server does not cache the group object if it's identifier is not unique and conflicts with user object. (#2851) 
        Resolution : Policy Server database schema has been updated to cache an object even if it's identifier is not unique. It will utilize a combination of the identifier and the entity type (user or group) to uniquely identify the entity in its cache.
       
    2. Issue : Accessing the Policy Server portal on an iOS device using the FileSecure iOS app (FileSecure Lite) displayed red lines below the repository list on the left pane. This was observed when the orientation of the device was changed. (#2502)
        Resolution : Policy Server has been changed to prevent the distortion and display repository list properly.  
        
    3. Issue : Policy Server shows '//' instead of '/' in filepath field for the File activity report.(#2967)
        Resolution : Policy Server has been changed to display '/' (single slash) instead of multiple slash in filepath field of File activity report.

Known Behaviour :
     1. There is a difference in user experience from FileSecure Desktop Client and from FileSecure iOS app (FileSecure Lite), for a user whose password is about to expire and he/she attempts to login. In case of FileSecure Desktop Client, after successful authentication, if user chooses not to provide new password (he/she close the authentication window), then login process will not be treated as complete and user will need to re-authenticate again. In case of FileSecure iOS app (FileSecure Lite), same scenario will result in proper authentication even if user does not provide the new password and instead clicks on the 'Done' button in the toolbar of the authentication window.   

=============================================================================================================================
FileSecure 2.50.0.0
FileSecure Policy Server 2.33.0.0
Sept 13, 2013

Features : 
    1. Support for SSO with IBM Tivoli Access Manager WebSEAL. (#2169)
        FileSecure Policy Server is integrated with IBM Tivoli Access Manager WebSEAL. In this integration WebSEAL server works as a reverse proxy and Single Sign-On server. It resides between the client machine and Policy Server. All the client request to Policy Server goes through WebSEAL. As part of providing SSO, WebSEAL checks the request from the client. If client is not authenticated then it prompts for the user credentials. Once user provides the credentials, WebSEAL verifies the credentials by connecting to the IBM Tivoli Access Manager Server. After authentication is verified, WebSEAL server forwards the request to Policy Server along with the authenticated user details. Policy Server uses these details and creates authenticated session for the User. This integration works with IBM Tivoli Access Manager WebSEAL version 6.1.
        
    2. Making system external user friendly. (#2797)
        As a step towards making FileSecure more friendly to any new user of the system, the Policy Server now provides intuitive assistance for the user who is trying to open a protected document. Link to this page is expected to be provided in the "buffer file". This module intelligently detects the user's environment and accordingly suggests the user steps to open a protected file. e.g. If the user is on Windows machine then he is provided an option to open the file in browser or download the desktop agent. If the user is on iOS then he is redirected to the FileSecure Lite page. For other environments, the user is typically requested to use WebConnect to view the file. 
    
    3. Download Desktop Client installation report. (#2834) 
        Policy Server allows to download report containing the details of all the computers where FileSecure Desktop Client is installed and configured with this Policy Server as Primary Policy Server. The report will contain details of the computer where Desktop Client is installed with FileSecure version 2.49.0.0 or above. 
    
Bug Fixes :
    1. Issue : Policy Server does not cache the entities (user/groups) added while defining/updating Credential. (#1533)
        Resolution : Policy Server has been changed to cache the entities added while defining/updating Credential.
    
    2. Issue : User is shown 'Session is expired' error when he/she performs following steps - Login -> Navigate to Search Credential -> Click on Create Copy -> Save -> View Files -> Back to Copy Credential. This issue is observed when the role is OU Admin as well as end user. (#1587)
        Resolution : Policy Server has been changed to display the previous credential page correctly instead of the error. 

    3. Issue : Entity details within Adhoc Credentials not updated when repository is synced. (#2702)
        Resolution : Policy Server has been changed to sync Adhoc Credentials correctly. 
    
    4. Issue : Credential definition page is reset to blank (User inputs are lost) when he/she performs following steps: - Login -> Navigate to Create Credential -> Click on Map/Unmap -> Back to Create Credential. (#2741)
        Resolution : Policy Server has been changed to show the newly created credential correctly instead of displaying blank credential page.
        
    5. Issue : Policy Server error page displays details of Apache Tomcat Server in case of HTTP 500, 501 errors. (#2800) 
        Resolution : Policy Server has been changed to display pages with error message in case of 500, 501 and other such errors.
    
    6. Task : As part of Policy Server distribution, provide ComponentConfig.xml with default values of all parameters. (#2761)
        Resolution : Policy Server has changed to provide ComponentConfig_default.xml with default values.
    
    7. Other fixes: #2798, #2799   
    
==============================================================================================================

FileSecure 2.48.0.0
Policy Server 2.32.1.0
Aug 5, 2013

Release Notes:
--------------------------------------------------------------------------------------------------------------
Bug Fixes:
    1. FileSecure does not grant Access Permission on the document to the user, if assigned to group other than Universal Group in Active Directory. (#2674)
        a. PolicyServer can connect to Simple AD Repository through Global Catalog port(3268 or 3269). 
        b. FilSecure Policy Server Repository configuration now provides an option to provide filter on groups. For correct behaviour, user should configure Universal groups of Active Directory as filter, if Global Catalog port is used for connection. 
        c. Only Simple AD Repository can use Global Catalog port to connect PolicyServer with Active Directory.
    2. Policy Server Credential definition page allows only 3 IP address range to define access rights for specific User/Group. Increase the IP address range limit to 10. (#657,#2574)
    3. Policy Server installation manual contains extra steps that are optional. These steps have been removed. (#2688)
    4. Other Fixes/Tasks. (#2654, #2687)

Note:
    1. FileSecure emphasizes to deploy JDK 1.7.0_21 to run the JVM with ?server mode to achieve better performance for Policy Server. However JRE 1.7.0_21 is also packaged in the Policy Server distribution, in case it is required to install JRE instead of JDK.
    
==============================================================================================================

FileSecure 2.46.0.0
Policy Server 2.32.0.0
June 17, 2013

Release Notes:
--------------------------------------------------------------------------------------------------------------
Features:
    1. Support for JRE 1.7.0_21.(#2634)
    2. Introduction of Client Component Configuration in Policy Server. (#2523)
       a. Component Configuration provides mechanism to configure any client component like Desktop Client, Automatic Data Classification etc. Some example of configuration are 'Enable/Disable One-Click feature', 'Make Automatic Data Classification mandatory or optional'. Component Configuration is maintained in Policy Server and client component retrieves this configuration from Policy Server and starts behaving accordingly.
       b. Desktop Client 2.30.0.0 and Policy Server 2.32.0.0 is mandatory to use this framework.

       * As of now, this framework is used by Automatic Data Classification only to make classification mandatory or optional.
    3. New improved version of End User Manual.(#2634)

Bug Fixes:
    1. Policy Server does not allow to change login context from one OU admin to another OU admin. (#1918)
    2. Some of the queries are not getting logged in the Policy Server log file.(#2556)
    3. Policy Server forces to detach the File from HotFolder when the HotFolder protected file is redistributed by the Owner of the File.(#1642)
    4. Policy Server list audit log page is unable to render UI in some of the specific search cases.(#2601)
    5. Desktop Client configuration report displays the version details of the other FileSecure components also. (#2423)
    
Note:
    1. Support for JDK/JRE 6 has been deprecated. It is mandatory for all the Policy Server/WebConnect deployments to upgrade to JRE7.
    
==============================================================================================================

FileSecure 2.45.1.0
Policy Server 2.31.1.0
May 7, 2013

Release Notes:
--------------------------------------------------------------------------------------------------------------
Bug Fixes:
    1. FileSecure protected files are not opening with FileSecureLite.(#2431)
    2. Calendar control is not getting displayed while defining date range to assign access rights to the users/groups.(#2378)
    3. Error when viewing secure send mail in Webconnect.(#1158,#1518,#1723)
    4. Error while accessing the view licensed users page on Policy Server.(#2437) 
    5. Others : #2474
    
==============================================================================================================

FileSecure 2.43.0.0
Policy Server 2.31.0.0
March 5, 2013

Release Notes:
--------------------------------------------------------------------------------------------------------------
Features:
    1. Support for IBM Tivoli Directory Server as Repository of User Identity Management System.(#1631,#2156)
    2. Support for mapping of credential with user(s)/group(s) across OUs.(#1754,#2220)

Bug Fixes:
    1. Default selected repository should be configurable.(#2167)
    2. Extra '>' sign displayed on add repository page.(#2225)
    3. Policy Server displays same records more than once in the list credentials page.(#1749)
    4. WebConnect: Java script error on android browser.(#2165)
        - Android 4.x is supported with WebConnect
        - Has been tested with default browser on Android
        - Javascript needs to be enabled (By default it is enabled)
        - Popups should be enabled (By default it MAY NOT be enabled)
        - A proper "file selection" application needs to be available 
    5. Others : #1725  

==============================================================================================================

FileSecure 2.42.0.0
Policy Server 2.30.0.0
Jan 31, 2013

Release Notes:
--------------------------------------------------------------------------------
Features:
    1. Support for Data Classification. (#1733)
    2. Support for new file formats : vsd, vdx, vss, vsx (#2034)  
    3. Displays full file path in the activity logs for file activities. (#1378)
    4. The font size on the Policy Server portal has been increased. (#1939)
    5. Introduced new Policy Server API to search user by login-id or e-mail address. (#2001)
    6. Others : #1718, #1557 

Bug Fixes:
    1. Policy Server does not accept the IPv6 address(es) in HTTP request. (#1708)
    2. Policy Server allows caching of web resources in the browser. (#1702)
    3. Policy Server does not support fail-over for FIM Repository. (#1719)
    4. Default filter for File and Credential Status in not 'Active'. (#1938)
    5. Others : #1596, #1934, #1941, #1739, #1704, #2036, #2049
    
Note: The Desktop Client version 2.21.0.0 and all prior versions are deprecated.

=============================================================================================================================

FileSecure 2.39.0.0
Policy Server 2.29.0.0
Oct 22, 2012

Release Notes:
--------------------------------------------------------------------------------
Features:
    1. Policy Server has introduced new repository type to integrate with third party SSO components for user authentication with Active Directory. (#1610)
    2. Changed the terminology from 'Author' to 'Protector'. (#1607)
    3. Provision to deploy FIM with self signed SSL Certificate for PoC. (#1692)
    4. Policy Server allows to select multiple entities on select entities page. (#1691)
    5. HotFolder Definition UI allows to change the external reference details. (#1635)
    6. File and Credential name can be searched with 'contains' instead of 'starts with'. (#1609)
    7. Protected files can be viewed on BlackBerry (default browser) using WebConnect. (#1531) 

Bug Fixes:
    1. Protected files edited in Desktop Client 2.22.5.0 (FileSecure 2.32.5.0) or later cannot be viewed in WebConnect. (#1628,#1577)    
    2. Synchronization issue while caching the users in memory. This lead to authentication failure in LDAP Repository. (#1560,#1606) 
    3. OU Admin of root level is not allowed to reset the lock for some of the protected files within the same OU. (#1590)
    4. Policy Server should not display the Copy Data activity filter on the portal. (#1608)
    5. Incorrect error message is shown for German language when user does not have any permission on the file. (#1614) 
    6. Policy Server portal some of the pages are displayed in mixed languages. (#1622)
    7. Others : #1546, #1700, #1683, #1613, #1605, #1580

=============================================================================================================================

FileSecure 2.35.0.0
Policy Server 2.28.0.0
Aug 03, 2012

Release Notes:
--------------------------------------------------------------------------------
Features:
    1. Facility to specify Author of the file while protecting the file. User can define Access Permissions for Author of the file in Credential. (#1489)
    2. Provision to manage HotFolderCabinet(s) and HotFolder(s) on Policy Server portal. HotFolderCabinets and HotFolders defined using HotFolderServer Enterprise Manager cannot be managed on Policy Server portal. (#1490) 
    3. Login page of 'FIM Repository' ('Seclore OpenDS Repository') in Policy Server is replaced with login page of FIM (FileSecure Identity Management). (#1491)
    4. Provision for tiny URL to access WebConnect. (#1567)
    
Bug Fixes:
    1. Unusual files get created in download folder of Policy Server. (#1535)
    2. SimpleAD Repository ignores (does not authenticate) users in OU name starts with 'System'. (#1542)
    3. Policy Server asks to change password of System Admin user even though password was reset recently. (#1558)
    4. Inappropriate error message is shown if user enters correct IP address but port value as 0 for the first/secondary Domain Controller. (#1530)
    5. Others : #1565  

Note: The 'Seclore OpenDS Repository' has been renamed to 'FIM Repository'. From Policy Server Version 2.28.0.0, the search base is mandatory for FIM repository. Login page of 'FIM Repository' ('Seclore OpenDS Repository') in Policy Server is replaced with login page of FIM (FileSecure Identity Management) hence this version of Policy Server requires FIM 1.6.0.0 or later to authenticate FIM Repository users.

=============================================================================================================================

FileSecure 2.34.0.0
Policy Server 2.27.0.0
June 29, 2012

Release Notes:
--------------------------------------------------------------------------------
Features:
    1. Provision to define access permissions at OU(Organizational Unit) level in Simple AD Repository. (#1467)
    
Bug Fixes:
    1. Copy Data permission should allow to extract data into protected documents only. (#1453)
    2. Search file using alpha-numeric characters in File Identifier field retrieves all records from database. (#1273,#1201)
    3. All fields in repository are cleaned up if a wrong value is entered in any one field. (#1274,#1202)
    4. Incorrect error message is shown if user enters port value as 0 in Simple AD Repository for the Primary/Secondary Domain Controller. (#1102)
    5. OUs are not shown in search result when user searches Groups with criteria value separated with comma(,). (#1468)
    6. Others : #1462, #1497

Note : FileSecure Desktop Client 2.18.3.0 and previous versions are deprecated.

=============================================================================================================================

FileSecure 2.33.0.0
Policy Server 2.26.0.0
May 11, 2012

Release Notes:
--------------------------------------------------------------------------------
Features:
    1. Policy Server support for 64 bit platform. (#1405)
    2. Provision to define access permissions at OU(Organizational Unit) level. (#1332)
        - The OU level access rights are enabled for following types of repository only. 
            - LDAPOpenDSRepository
            - LDAPDominoRepository
            - LDAPSunOneRepository
            - LDAP Seclore OpenDS Repository
            - LDAP AD Single Domain Repository 
    3. Support for DIGEST-MD5 authentication in Simple AD Repository. (#1409)
    4. Integration with SIEM(Security Information and Event Management) systems. (#1410)
    5. Mechanism to identify the set of request coming from the same client from the log file. (#1399)
    6. Support for iOS client to view FileSecure protected files. (#1439)
    
Bug Fixes:
    1. Logging of the remote Host Name and IP address in case of invalid URL is requested. (#1437)
    2. Policy Server redirects to error page if Desktop Client update patch is not available. (#1448)
    3. Password policies contains message 'Login id should not be part of Password.' twice. (#1345)
    4. Classification description is not marked as mandatory(*) on add/update Classification page. (#1435)
    5. OpenDS Server connection does not respond back to Policy Server. (#1406)
    6. Policy Server does not display appropriate message when the password of FIM user is expired. (#1449)
    7. SimpleADRepository does not allow to change the name of the domain. (#1438)
    8. Others : #1408, #1440, #1436

NOTE : Only Policy Server is supported on 64-bit platform. WebConnect is not supported on 64-bit platform.

=============================================================================================================================

FileSecure 2.32.1.0
Policy Server 2.25.1.0
Jan 24, 2012

Release Notes:
--------------------------------------------------------------------------------
Bug Fixes:
    1. SimpleAD Repository Connector, when configured, makes searches slow. (#1287)
    2. In case of License expiry, PolicyServer home page is distorted. (#1301)
    3. PolicyServer does not remember the last selected repository for a user. (#1289) 
    4. SSL connection does not work with the active directory. (#1291)
    5. Other Fixes. (#1286, #1288, #1293)
Note: Tomcat is upgraded from version 7.0.21 to 7.0.23.    

=============================================================================================================================

FileSecure 2.32.0.0
Policy Server 2.25.0.0
Dec 19, 2011

Release Notes:
--------------------------------------------------------------------------------

Features:
    1. PolicyServer home page displays less text. User can choose his Repository and enter credentials on the home page itself. (#993)
    2. Enforced password constraints for password of System Administrator, HotFolder Cabinet. (#1231)
    3. Allow HotFolder Cabinet user to view file protection details and activity logs of files protected with any HotFolder in that HotFolder Cabinet. (#1212)
    4. Turned off auto-complete for user name field for System Administrator login page. (#1261)

Bug Fixes:
    1. HotFolder definition UI does not allow to update name, description and owner of HotFolder. (#1226)

=============================================================================================================================

FileSecure 2.31.0.0
Policy Server 2.24.0.0
Oct 17, 2011

Release Notes:
--------------------------------------------------------------------------------

Features:
    1. Support for Tomcat 7 with JDK 1.6.0_27. (#1153)
    2. Added the web wizard for helping new user for registering with the FileSecure Identity Management, installing the Desktop Client and verifying the installation of Desktop Client. (#873, #1155)

Bug Fixes:
    1. Active Directory 2008 cannot be configured as SimpleADRepositoryAdapter repository. (#771)
    
Note: 
    1. Support for Tomcat 5.5 and JDK 1.5 is deprecated.

=============================================================================================================================

FileSecure 2.30.0.0
Policy Server 2.23.0.0
Sep 21, 2011

Release Notes:
--------------------------------------------------------------------------------

Features:
    1. Support to view protected file in browser. (#1003)

=============================================================================================================================

FileSecure 2.28.0.0
Policy Server 2.22.0.0
Jul 27, 2011

Release Notes:
--------------------------------------------------------------------------------

Features:
    1. Added support to protect file using the external identifier of the Hot Folder and external identifier of the File.

=============================================================================================================================

FileSecure 2.26.0.0
Policy Server 2.21.0.0
Jul 4, 2011

Release Notes:
--------------------------------------------------------------------------------

Features:
    1. Support for multi-lingual data in Policy Server, with MS-SQL database. (#1004)
    2. OU hierarchy list window is expandable and the OUs are displayed dynamically. (#814)
    3. Authentication of inactive users in the Seclore OpenDS is restricted in Policy Server. (#1044)    
    4. Provision to specify the fail-over IP address/machine name for all types of repositories in Policy Server. (#1041, #1043)    

Bug Fixes:
    1. Policy Server allows to put start IP address greater than end IP address in the credential definition page. (#906)
    2. If the license is expired, 'User not authenticated' message is displayed at the time of auto authentication by the Desktop Client. (#984)
    3. Change system user password. Old and new password are getting checked in a case insensitive manner. (#894)
    4. HotFolder Enterprise Manager crashes when the 'Process' button is clicked, if there are more than one copy of the file protected with same File Id. (#1082)
    5. No 'Download' button provided for downloading user license details. (#880)
    6. Some files from PolicyServer portal are downloaded without full-name/extension. (#1028)
    7. Downloaded reports name does not contain the date of report download. (#991)
    8. Activity is incorrectly displayed as "File Transfer" when ownership of file is transferred. (#220)
    9. PolicyServer is not able to fetch the entries from LDAP, if they contain the special characters in the Entry DN. (#596, #780) 
        - The issue has been resolved for following repositories
            - LDAPOpenDSRepository
            - LDAPSunOneRepository
            - LDAP Seclore OpenDS Repository
            - LDAP AD Single Domain Repository
        - The issue has not been resolved for following repository.
            - LDAPDominoRepository
    10. LDAP Connections are now not getting pooled for the users authenticating from the Policy Server for Simple AD Repository. (#1019) 
    11. The Policy Server does not display records more than 100 and asks to refine the filter. Provide provision to display up to 500 records. (Support Id#1094)

Note: 
    1. Support for MS-SQL Server 2000 is deprecated.    
    
=============================================================================================================================

FileSecure 2.24.0.0
Policy Server 2.20.0.0
Mar 9, 2011

Release Notes:
--------------------------------------------------------------------------------

Features:
    1. Support for multi-lingual Policy Server, for all modules. (#884)
    2. Link on Policy Server portal to register a "New User" in FileSecure Identity Management(FIM), in case the repository is of type "LDAP Seclore OpenDS Repository". (#948)
    3. Link on Policy Server to download Policy Server's Profile, which can then be imported in Desktop Client System Tray. (#949)

Bug Fixes:
    1. Policy Server does not start completely, if the database server is down or not reachable.(#940)
    2. Transfer file ownership, the system allows to select group as new owner of the file.(#941)
    3. List audit log display the repository code twice in the Organizational Unit qhcode, if the Organizational Unit is deleted.(#942)
    4. User is not allowed to authenticate and search with user principal name.(#943) 
    5. List pages shows incorrect selected records, if sorting is performed on them.(#944) 
    6. All User Group is visible to all the containers in credential entity mapping.(#945) 
    7. Instead of proper business message the generic message "Invalid operation. Please contact administrator." is displayed.(#946)
        - When the user enters wrong password while changing system user password.
        - When the user enters invalid email id suffix while adding the repository.
    8. In IE9, the Actions columns look distorted for the Classification page.(#947)
    9. Policy Server allows to add opends repository instance without providing the password.(#933)

=============================================================================================================================

FileSecure 2.22.0.0
Policy Server 2.19.0.0
Jan 4, 2011

Release Notes:
--------------------------------------------------------------------------------

Features:
 
    1. Support for multi-lingual Policy Server.(#743)
        a. This version of Policy Server only supports German (de) language other than English (en-US).
        b. Only Oracle database is supported and not MSSQL for multi-lingual Policy Server support. 
        c. Only LDAP Repository adaptor supports multi-lingual and not Simple AD Repository adaptor.
        d. Complete Policy Server has not been modified for multi-lingual support. Modules which are included for this are - 
            i. Home page
            ii. Framework structures - Header, footer, navigation bar, error/success messages on all pages. 
            iii. LDAP Repository - Login, Select Entity, Select OU page.
            iv. Credential - Add, Update and View Credential. This also includes Secure Send screens.
            v. View File Details page on right click of protected file from Desktop Client.
            ** For all other screens only header, footer and navigation bar will be in the multi-lingual supported language.
        e. Undeterministic behavior when user changes the browser locale while still on some PS page. May see messages in more than 1 language.
        f. Not setting locale in HttpResponse header for Old Web Services APIs.
    2. User friendly and better "Download Desktop Client" link on the Home Page.  

=============================================================================================================================

FileSecure 2.21.1.0
Policy Server 2.18.3.0
Dec 20, 2010

Release Notes:
--------------------------------------------------------------------------------

Bug Fixes:
    1. Open File activity is not getting logged in Policy Server.
    2. List of files associated with a Credential not displayed [Invalid operation err thrown].(#863)
    
=============================================================================================================================

FileSecure 2.21.0.0
Policy Server 2.18.2.0
Dec 10, 2010

Release Notes:
--------------------------------------------------------------------------------

Bug Fixes:
    1. End User is not allowed to transfer files to users outside of his own OU. Similarly OU admin is not allowed to transfer files outside his area of administration. (#842)
    2. The OU selection page takes a lot of time in loading.(#843)
       - Resolved for following type of repositories.
         - LDAP OpenDS Repository
         - LDAP SunOne Repository
         - LDAP Domino Repository
         - LDAP AD Single Domain Repository 
         - LDAP Seclore OpenDS Repository 
    3. User is not allowed to view the predefined credential details in view file protection details page, if the credential is not mapped to the user. (#857)
    4. User is not allow to update the credential, if any of the entity is not in visible repository. (#858)
    5. If the file is protected with HotFolder having mapping with some predefined credentials and the owner of the file is not mapped to those predefined credentials, then exception is thrown. (#859)
    6. Allow search on current file name and current file extension in file activity filter page. (#618)
    7. LDAP AD Repository Login page should display the domain name and sample of valid and invalid user names.(#853)
    8. Autodesk Revit Architecture files with extension rvt and rfa are supported in the PolicyServer. (#856)
    9. Default logging level for Request logs and PolicyServer logs are changed to info level. (#855)
    10. The help and download dc links should come on the top of the page on PolicyServer home page. (#854)
    
=============================================================================================================================

FileSecure 2.20.1.0
Policy Server 2.18.1.0
Sept 29, 2010

Release Notes:
--------------------------------------------------------------------------------

Bug Fixes:
    1. The response from Active Directory is very slow, every time a user or OU is fetched by PolicyServer portal. To resolve this, current SimpleAD Repository need to be migrated to "LDAP AD Single Domain Repository". (#656, #704)
    2. Can not select the owner while creating the predefined credential, if the OU administrator is part of the another Repository. (#775)
    3. Tomcat Manager login page is displayed when user accesses Policy Server URL without Application Context. An optional step is added in the Policy Server Installation Manual to restrict the same. (#685)

Note: 
    1. "LDAP AD Single Domain Repository" does not support sub-domains and trusted domains.

=============================================================================================================================

FileSecure 2.20.0.0
Policy Server 2.18.0.0
Sept 3, 2010

Release Notes:
--------------------------------------------------------------------------------

Features:
    1. Enhanced the protection license user interface to view existing licenses and assign new protection licenses. (#408).
    2. Informative and detailed message is returned in case user does not have access to a file. (#421). 
    3. System admin and OU admin login requests are captured in the audit log. (#658, #645).
    4. PolicyServer stores the basic User/Group/OU details like Name, EMail, Description in the database. This information will be displayed, if the PolicyServer can not fetch the User/Group/OU details from the Repository. (#549).
    5. Detailed error messages are shown on File, Credential, File Activity, Classification and License related screens. (#550).
    6. Displays all the captured IP addresses in detailed view of File Activity and include in File Activity report.(#265).
    7. Added details - email-id, login id and OU hierarchy path of the File Owner and the User(who has performed the activity) in the File Activity report. (#635, #644).
    8. Displays the current PolicyServer version along with the FileSecure version on the PolicyServer.     
    
Bug Fixes:
    1. PolicyServer can not be restarted, without re-starting Application Server. (#543).
    2. Users with "Protect with Predefined Credentials" license are not allowed to send protected emails. (#562).    
    3. View File Activity does not show the public IP address from where the Activity is performed. (#590).
    4. Refine filter does not work, in case of special characters in filter pages (#617).
    5. Unable to remove Protection license of deleted User. (#551).
    6. Unable to map entities to the Predefined Credential, in case Credential identifier is greater then 999. (#624).
    7. Exception 'NULL' error message is displayed when the child folder is set as HotFolder before its parent folder. (#244).
    8. Credential Entity mapping page is not displayed, if any Group mapped with the Credential is deleted from the Repostiory. (#619).
    9. User is not allowed to login from System Tray once the login attempt fails, unless User re-starts System Tray. (#333).
    10. User is asked to login again while selecting Owner in the HotFolder Integration UI. (#410).
    11. List audit page displays the criteria filter as 'ou starts with'. (#556).
    12. If the change in Classification Status fails, the reason for it's failure is not displayed. (#553).
    13. If the assign Protection license fails due to limitation on number of license, then exception message is displayed as "Unexpected error. Please contact system administrator.". (#536).
    14. In case of create HotFolder Cabinet and reset HotFolder Cabinet passphrase, validation of passphrase length message comes twice. (#660).
    15. While creating Adhoc Credential, Protection Default Classification is not selected.(#672).
    16. PolicyServer clears the Session from the Browser, if the Credential is selected for editing from protection screen of Secure Send.(#671).
    17. On click of select OU button, Simple AD repository is every time getting new OUs instead of using the cache to display the OUs, hence it takes more time.(#697).
    
Notes :  
   1. Desktop Client version 2.6.1.0, 2.6.2.0, 2.7.0.0, 2.7.1.0, 2.7.2.0, 2.7.3.0, 2.7.4.0, 2.8.0.0, 2.9.0.0, 2.9.1.0, 2.9.2.0, 2.9.3.0, 2.9.4.0, 2.9.5.0 are deprecated.
   2. Provided JCE files should be copied in the JRE before migrating the Policy Server. 
   3. All the existing PolicyServer deployments are required to regenerate the license. 

=========================================================================================================================

FileSecure 2.19.0.0
Policy Server 2.17.0.0
Apr 30, 2010

Release Notes:
--------------------------------------------------------------------------------

Features:
        1. Support for setting default protection (includes classification and credential) at user level, where in the files can get protected with this, without user explicitly specifying classification or credential. Please refer the administrator manual details. (#398).
        2. Support for Sun One LDAP system. (#389).
        3. Protecting emails through SecureSend has been optimized to re-use credentials, appropriately. (#423).
        
Bug Fixes:
        1. While redistributing file, redistributor is not allowed to add the credential if the classification applied on the file is inactive. (#545).
        2. List Audit Log displays 'Total no. of files' in caption. (#529).
        3. If a credential is mapped with a group, the member user of the group can not be mapped to the same credential. (#523).
        4. PolicyServer goes in infinite loop, when there are two groups which are member of each other, and one of them is getting mapped to the credential. (#524).
        5. In case of save and advance in email protection, protection page does not displays the adhoc credential in the available credential list. (#531).
        6. Rectified the "Missing parameter 'credentials'." error in case of getcredentialdetails request of web services. (#532).
        
Note : Assigning custom license is deprecated and all the existing assigned custom license will be removed.

=============================================================================================================================

FileSecure 2.18.0.0
Policy Server 2.16.0.0
Mar 19, 2010

Release Notes:
--------------------------------------------------------------------------------

Features:
        1. Integration with any LDAP system easier and in most cases user configurable. (#509).
            a. Added support for 'IBM Domino' LDAP system.
            b. Added support for 'Open DS' LDAP system.
        2. Download DC Installer will create the new zip file everyday, which in turn reduces the maintenance effort of manually deleting the zip file. (#502).
        3. Display file owner name and email address in case the user is not able to open the file. (#420).
        
Bug Fixes:
        1. Bulk transfer of files, protected by the same custom credential, results in creation of huge number of custom credentials. This behavior halts the system. (#378).
        2. If a redistributor is made owner of a file, he is unable to drop credentials applied by him, when he was the redistributor.(#376).
        3. Ambiguous message when an unauthorized user tries to open the file. (#387).
        4. If one of the repository fails to initialize, PolicyServer is not able to load other repositories. (#507).        
        5. Title of the repository details page is "Repositories Details". (#416).        
        6. List repository page throws error, while displaying the synchronization icon. (#508).

=============================================================================================================================

FileSecure 2.17.0.0
Policy Server 2.15.0.0
Feb 05, 2010

Release Notes:
--------------------------------------------------------------------------------

Features:
        1. To audit administrative activities, Audit Logs feature has been provided to administrator and ou administrator. To view the details of the same, please refer the administrator manual.
        2. List pages for files, activity logs, credential and audit logs, have been updated for customized sorting for the end user. 
        3. Displayed mandatory fields with asterisk, through out the portal. (#21).        
        4. Feature provided to clear Repository cache from the list repository page, on click of a button. 
        5. In Download Desktop Client page, folder is automatically zipped and downloaded, which reduces the effort of updating the zip file every time, new Desktop Client is released. 
        6. Unhandled exception are displayed on the standard error page.
        7. Policy Server is optimized for response time 
            a. All the classifications are cached in the memory. 
            b. Deleted users, groups and containers are cached in memory. (#368/369).
        8. Range for errors code is defined, which are meant for end user. 
        9. Application(s) supported by Desktop Client is based on the License deployed at the Policy Server. 
                By default supported applications are - Acrobat Reader, Acrobat Professional, MS Paint, Microsoft Office 2k3 and 2k7. All other supported applications require explicit license.
        10. Displayed current file name in the single view of the activity log.
        11. All the web services request supported by Policy Server, are processed by the same URL.

Bug Fixes:
        1. OU Admin is allowed to transfer ownership of file to self. 
        2. OU Admin can not be removed, even if the user is deleted from the active directory.
        3. Credential is not mapped to the owner entity, in case the predefined credential is transferred to the custom credential.
        4. Description and password field are not cleared with others, after clicking "Clear All" button in repository page. 
        5. License manager is not logging the exception in case of load errors.
        6. System Admin is not allowed to view credential entity mapping on view credential page.
        7. In case of invalid url, User is redirected to the page not found page.
        8. Incorrect error message, when no records are found, on the select credential page. (#197).
        9. Incorrect error message, when revoking the protection rights. (#284).
        10. Incorrect message when search result of entities is more than the displayed entities. (#335).
        11. Unchecking a selected entity does not clear the "Select All" check-box on select entities page of "User Protection License Details" page. (#338).
        12. Incorrect error message on view activity log, when the user is not the owner of the file. (#36/305/306).
        13. Entity QId is not validated for the format. (#270).
        14. Authenticate fileserver user request is required to skip the machine identifier validation. 
        15. Authenticate fileserver user request is required to skip the policy server identifier validation.        
        
=============================================================================================================================

FileSecure 2.15.0.0
Policy Server 2.14.0.0
Dec 24, 2009

Release Notes:
--------------------------------------------------------------------------------

Features:
    1. User has an option to have more granular control over the file, while defining credentials. The new access rights which
    are part of this release are (#184) - 
        a. Screen Capture - This allows the FileSecure protected file to be opened on VM, RDP Or any other software which allows remote session. 
        This allows to capture screen through Print Screen key.
        b. Copy Data - Allows data of FileSecure protected file to be copied outside.
        c. Allow Macro - Allows to define and run macro for a FileSecure protected file.
    2. To aid MIS reporting new activities like access remotely, access on virtual machine, capture screen, copy data and macro, have been added. ( : #184)
    3. Updated the view file details page to display the file status and redistributable permission.
    
Bug Fixes:
    1. Default Session Timeout changed to 15 minutes from 1 hour.
     
=============================================================================================================================

FileSecure 2.14.0.0
Policy Server 2.13.0.0
Nov 20, 2009

Release Notes:
--------------------------------------------------------------------------------

Features 
    1. Added support for OpenDS repository - an free source LDAP implementation.
    2. User is allowed to lock a protected file to a machine, on first time use.
    3. Updated the hotfolder definition page to view the selected credential. 
    4. Added the desktop client version, server version and client version on the view file activity page. ( : #257)
    5. Updated the download file activities report to provide detailed information.
    6. Added link to download report containing the machine configuration and desktop client version for system administrator role. ( : #256)
    
Bug Fixes:    
    1. UserName label and text are displayed on same row on high resolution display, while password is displayed in different row. ( : #322)
    2. Fatal error while updating the hotfolder for classification. ( : #308)
    3. ProtectWithId is not working with the oracle database.
    4. After defining hotfolder and during redirection to the integrated system, wrong message is displayed.( : #321)

Note: From this version onwards, PolicyServer requires minimun java version as 1.5.08
    
=============================================================================================================================

FileSecure 2.13.0.0
Policy Server 2.12.0.0
Oct 09, 2009

Release Notes:
--------------------------------------------------------------------------------

Features 
    1. Ability to set preserve user session option for a Repository.
    2. Exposed RESTEasy web services APIs for web service client. 
    3. Provided HotFolder interface for integration with third party systems. 
    4. Provided provision to use display name as name property for Active Directory users. 
    5. Ability to search multiple users from AD at one go by providing comma separated list

=============================================================================================================================

FileSecure 2.12.0.0
Policy Server 2.11.0.0
Sept 18, 2009

Release Notes:
--------------------------------------------------------------------------------

Features 
    1. Ability to define default classification.
    2. Logging the FileSecure version in the each log file. 
    3. Disable auto-complete option in browsers for password fields.  
    4. Option to configure email id for all users group in Simple AD. 
    5. Optimization for login of user in case of auto authentication, if there are more than 1 AD repository present in PS.
    6. Select OU page is optimized with caching the OUs in tree. 
    
Bug Fixes:
    1. The HotFolderServer crashes after login using the credentials of System Admin.
    2. TransferContainer request does not transfer the container, if the old container hcode is different in the corresponding table.
    3. Sync repository issue. After syncing the repository, while searching the user, it displays old container as container of the user.
    4. On Redistribute page the classification icon is displayed for redistributor, instead of being displayed as disabled.
    5. Improper message "Invalid Credential '- 1'. No Permissions defined." appears when user deletes an entity in the Credential search screen and all other entities are Entities not found in the AD and Done button is clicked. 
    6. Repository Login page. On click of help link, it reloads the Select Repository page.
    7. Policy Server portal is taking time to login, if repository is Active Directory. 
    8. Masking of the sensitive information is done through the '*' character while logging in file as well as database table.

=============================================================================================================================

FileSecure 2.11.0.0
Policy Server 2.10.0.0
Aug 14, 2009

Release Notes:
--------------------------------------------------------------------------------

Features 
    1. Support for Custom HotFolderCabinet. Added UI to create/update/reset passphrase Custom HotFolderCabinet. This UI is available to System Admin only.  
    2. Some Policy Server APIs supported as RESTEasy web services. 
    3. Certain details like data key and repository details are stored as encrypted in the database.
    4. Added download link to download all the users having protection license. The link is available to System Admin and OU Admin.
    5. Support for subdomain in Active Directory Repository.
    6. 'All Users Group' added for the configured domain.

Bug Fixes:
    1. The update repository allowed to change the domain name of the SimpleADRepository.
    2. On File Activity Criteria, while choosing the owner, there is no check to validate that the owner is from the logged in user's OU.
    3. Oracle Database Script as well as code needs to be updated to resolve the 'as' keyword issue.
    4. On Select Entity page, it displays the OU name in the selected filter criteria string even if no OU is selected.
    5. Remove the GroupType, Display name for Group from the drop down list in search entity page.

=============================================================================================================================

FileSecure 2.10.0.0
Policy Server 2.9.0.0
Jun 26, 2009

Release Notes:
--------------------------------------------------------------------------------

Features 
    1. Support to protect multiple files with same file id.  
    2. Link available to download the Seclore FileSecure Desktop Client. 
    3. View Credential page.
        - Select all check-boxes provided for Edit, Print, Full Control, Offline, Full Control right.
        - Updated to display the select start-end date with in the same page. 
        - Provided common link to select and clear start-end date for all the access rights. 
        - Provided common link to select IP Range for all the access rights.
    4. Enhanced security to restrict direct access of the Policy Server resources through the portal.
    5. Support to add Trusted Domain Active Directory as Repository.

Bug Fixes:
    1. Policy Server does not startup in case it fails to initialize itself. Instead now it shows the error message on the portal.
    2.  Get Access Permission bug: If owner gives redistributor rights to a user, then that user was able to give himself higher rights than what the owner gave him permission for and also the same was getting applied at the time of that user accessing any file with that credential.
    3. When any end user searches for his/her credentials, all the credentials mapped with the user are displayed but not with the group of the user.
    4. In case of credential where the no of days since protection was specified, access permission was getting calculated in-correctly.

=============================================================================================================================

FileSecure 2.9.0.0
Policy Server 2.8.0.0
May 25, 2009

Release Notes:
--------------------------------------------------------------------------------

Features 
    1. Support for HotFolderServer. 
    2. Support for OpenOffice extensions. 
    3. Feature to search files based on HotFolder name. 
    4. Added the OU name and OU hierarchy code in the File download report. 
    5. The HotFolder name is displayed in the view File Details, Redistribute and multiview of the Files pages.
    6. New and improved manuals for Admin and End User.

Bug Fixes:
    1. If the value of the Credential id is more than 999, the file is not getting protected. 
    2. Take care of XML escape, while creating XMLs. 
    3. Right Click on a protected file, select "Activity as different user  -> View Activity Log" from the menu. The browser is opened for login. After successfully login, it closes the browser, instead it should display the activity logs of the selected file. 
    4. While updating the user protection license, if any update fails, then it skips rest of the users and also does not display it on the portal. 
    5. Filter File Activity. While selecting the Actor user, the system allows to select Group also.
    6. In SimpleADRespository while getting entities from AD, the system takes lot of time to return the result if there are no entries to be returned. 

=============================================================================================================================

FileSecure 2.8.0.0
Policy Server 2.7.0.0
Apr 6, 2009

Release Notes:
--------------------------------------------------------------------------------

Features 
    - Support of the Oracle 9i and Oracle 10g. 

Bug Fixes:
    - Credential entity mapping jsp page. The display message needs to be updated when the credential is inactive. 
    - View file protection details page. The display message needs to be updated. 
    - In case of the user has logged in as OU admin of other then the his own repository,  while creating predefined credential, the system is searching the OU within the user's repository. But the OU is supposed to be searched from the other repository. 
    - The Seclore web site link is moved at the bottom of the every portal page.

=============================================================================================================================

FileSecure 2.7.0.0
Policy Server 2.6.0.0
Mar 16, 2009

Release Notes:
--------------------------------------------------------------------------------

Features 
    - Server 
        - Logging of the Transfer file ownership as file activity.
        - Allow update of Repository with status as "UnInitialized".
        - Support of complete repository module 
            - Delete Repository feature.
            - Map-Unmap Repository feature.
        - Modified error messages - 
            - To display the request name instead of type.
            - To display object ( credentials, files etc ) names along with ids.

    - Portal 
        - Logging of the Transfer file ownership as file activity, the filter activity page has now options to search by transfer ownership activity. 
        - If there is only one repository while showing select repository page, user is automatically redirected to that repository page.
        - Allow update of Repository with status as "UnInitialized".
        - Support of complete repository module 
            - Delete Repository feature.
            - Map-Unmap Repository feature.
        - Combined the file based filter on credential with the basic filter.
        - Combined the credential filter with entity filter.
        - In the view credential page, view right is automatically selected. 

    - Simple AD Repository
        - Optimization for searching ous from AD

Bug Fixes:
    - Server 
        - None
        
    - Portal    
        - Logged-On time on activity single view displayed incorrectly.
        - Fixed vulnerability from CrossScripting bugs by encoding user visible strings (input parameters and error messages).
        - System repository was visible when the login request was made from Desktop Client, which is not required.
        - Rectified the code for SQL CLOSE DB Connection (In validate redistribute file action).
        - Fixed the bug for File Transfer ownership for error "Can not transfer ownership as the user is not the ou admin'. 
        - Error displayed while selecting inactive Repository. Resolved by displaying only active repositories. 
    
=============================================================================================================================

FileSecure 2.5.0.0
Policy Server 2.5.0.0
Feb 9, 2009

Release Notes:
--------------------------------------------------------------------------------

Features 
    - Server 
        - Database script updated, created migration script to contain the ip-addresses and host-name columns for file activity logs
    
    - Portal 
        - Help link provided on the portal for all the roles.
        - Enhancement for customization. Provided mechanism to write custom code on the top of the product.
        - The host-name and ip-addresses are shown in the single file activity log view. 
        - Provided an option in the file protection dialog to edit a credential in the browser.
        - System Admin is allowed to view the Policy Server license details. 

Bug Fixes:
    - Server 
        - In Transfer Ownership of Credential to user, If the user does not have the protection rights then he should not be allowed to Transfer the Credential to Custom User.
        - Changed the logic to compare the root container of the repository.
        - The logging of the FileMaster insert query is removed, as the query contains.  

    - Portal    
        - The file protection details is not displayed, when the same credential applied on the file by more then one user.
        - If the user logs in from desktop client then Change Login Context link should not be visible.
        - List of activity in Filter Activity Page - * should be at the top.
        - Escaped the special characters while querying the database, in case of the filtering the criteria.
        - Download report pages optimized to preserve data in the String Buffer. 
        - In the credential details page for an Access Permission, validate that the first number in the FROM and TO ip addresses is same.
    
    - Simple AD Repository
        -  Simple AD for searching users using SID, the SID token is parsed through the long, instead of int.
        -  The throwing Exception mechanism updated, not to return special characters, which can not be parsed.