Liquid error: undefined method `name' for nil:NilClass

Desktop Client 3.11.0.0

  1. Introducing the In App-protection for Microsoft Office apps. 
    1. Seclore presents the Seclore It button in all Microsoft Office apps for single-click protection from within the open file. 
    2. User can enable the button while editing an unprotected document. 
    3. Once the user closes the unprotected file with the Seclore It button enabled, the file gets protected and the user is prompted to change the file permissions and add recipients. 
    4. File permissions can also be added to the protected file while emailing, using Smart Sharing. 
  2. Extending Seclore’s email protection  capability to third-party tools. 
    1. Third-party tools can now integrate with Seclore’s email protection interface in Outlook allowing them to leverage end-to-end security for emails and attachments in collaboration with their product features. 
  3. Introducing HTML preserve feature for files protected using Universal Protection. 
    1. Now files protected using Universal Protection will open directly in the edit mode when opened using the native app. 
    2. Users can edit and save changes directly in such files without the need for unprotecting and opening them in the native app for editing. 
  4. Introducing Share and Protect + Share feature in the Endpoint SDK along with notification module.  
  5. Incorporated the new HTML buffer file, that displays user instructions for file open in the Raw HTML content. This is useful in scenarios where the Seclore Protected file is opened in a 3rd party viewer that cannot render HTML content. 
  6. Fixed the issue where the PS login page was displayed instead of a prompt asking the user to allow login using the credentials logged into the Desktop Client. 
    1. Before the fix: When the user was already logged into the Desktop Client and opens the PS URL in the chrome browser, a prompt was displayed asking the user to allow login using SSO of the Desktop Client. 
    2. Instead the PS Login page was displayed, and the user had to login again using his credentials. 
    3. After the fix: Now the user will be directed to the SSO prompt allowing to login directly using the Desktop Client login. 
    4. The Policy Server URL must be the same as the one logged in using the Desktop Client.  
Login or Signup to post a comment