Seclore FileSecure 2.67.0.0 is released...!!!

Hi everyone,

 

Taking one more step towards being most integration friendly IRM solution, Seclore FileSecure 2.67.0.0 brings power to leverage existing Rights Management capabilities of enterprise applications like SharePoint, Virtual Data Rooms and Reporting Systems etc. and removing headache of managing rights in multiple systems. Enterprise Application and Access Rights Adaptor allows developers to integrate such that permissions defined in external applications can be enforced by Seclore FileSecure on file protected by external application. Please refer attached ‘FRD - Enterprise Application v1.3.pdf’ for more details.

 

and as usual, few notorious bugs have been thrown out.

 

More details…

 

Policy Server:

Features:

1. Introduced Enterprise Application Integration Interface. (#3492, #3598)

Significantly enhanced the integration capability of FileSecure by allowing to inherit the access permissions from another Enterprise Application.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.Any changes in the user permissions in the Enterprise Application will be automatically applied on the downloaded files.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.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.Restart of the Policy Server is required if any detail for the above integration is changed in Policy Server.From this release onward, 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:

Allow user creation in FIM (FileSecure Identity Management) repository. Target repository can be configured on the Policy Server.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 IRM Protector for SharePoint:

Bug Fixes:

1. Issue: Files protected from FileSecure IRM Protector for SharePoint does not open or unprotect if Policy Server identifier has '&', '<', '>', '"' or ''' (XML special characters). (#3622)

Resolution: FileSecure IRM Protector for SharePoint has been changed to take care of this issue.

2. Issue: Cannot connect to Policy Server even if Policy Server is deployed with valid SSL certificate when is-production flag is set TRUE in configuration. (#3623)

Resolution: FileSecure IRM Protector for SharePoint has been changed to take care of this issue.

 

Web Service Client Library:

Bug Fixes:

1. Issue: Files protected from .NET library does not open or unprotect if Policy Server identifier has '&', '<', '>', '"' or ''' (XML special characters). (#3606)

Resolution: .NET library has been changed to take care of this issue.

2. Issue: Cannot connect to Policy Server even if Policy Server is deployed with valid SSL certificate when is-production flag is set TRUE in configuration. (#3607)

Resolution: .NET library has been changed to take care of this issue.

3. Issue: Documentation is not in user-friendly format. (#3608)

Resolution: Documentation is available in .CHM format rather than .XML format.

4. Issue: Required to compile the software which use .NET library because of strong name signing. (#3621)

Resolution: Publisher policy assembly library is distributed with package.

 

Enterprise Application Access Right Adaptor Interface (Web Service):

Features:

1. EA ARA Web Service interface allows external application to integrate with FileSecure Policy Server so permissions defined in external application can be enforced on files protected by external application rather than defining and managing permissions in Policy Server. This interface is in form of HTTP/S Web Services. It requires implementation of two Web Services: 1) Ping to return various information and 2) GetAccessRight to return permissions of the given file.

 

Component Details: 

1. Policy Server: 2.38.0.0

2. FileSecure IRM Protector for SharePoint: 2.0.1.0

3. Web Service Client Library: 1.11.1.0

4. EA ARA Interface (Web Service): 1.0.0.0

Login or Signup to post a comment