1. Introducing two-factor authentication (2FA) with Time-based One-time Password (TOTP) for Seclore FIM.
a. Enterprises can now enable two-factor authentication for internal users and external collaborators and partners.
b. Users would be prompted to register their TOTP app when they try to log in for the first time after 2FA is enabled for an enterprise. Any TOTP app can be used for this purpose.
c. Users would then be prompted to enter the code generated by their authenticator app as a second factor of authentication every time they try to log in.
d. 2FA can be enabled by System Administrators from the Repositories section of the System Administrator portal.
2. Introducing support for OpenID Connect.
a. Enterprises can now enable user authentication with any authentication provider that supports OpenID Connect protocol.
b. Apart from the Google and Microsoft authentication options available earlier, enterprises can set up other authentication providers like Okta, PingFederate, other out-of-the-box or custom applications that support OpenID Connect.
3. Enterprises can now choose to disable the default log-in fields (Email ID and Password fields shown by Seclore) and only show the third-party authentication options such as Google, Microsoft, or any other supported authentication provider.
4. Enterprises can now enable user authentication in Seclore FIM with only email-based one-time passwords (OTP).
a. This feature can be enabled by System Administrators in the ‘Repository Details’ section in the ‘Repositories’ tab.
b. Once it’s enabled, new users wouldn’t get an option set a password. They’ll receive an OTP on email every time they try to log in.
5. Activities performed by enterprise applications will be logged in the Policy Server with the enterprise application’s name.
a. During content scanning, enterprise applications may protect, unprotect, or share files. Such activities will now be logged in the Policy Server with the enterprise application’s name, unlike earlier, when it was logged with the file owner’s name.
b. Only System Administrators will be able to see the logs of activities performed by enterprise applications.
c. The file access summary sent daily to file owners won’t contain the activities performed by enterprise applications.
6. Made changes to the buffer file for desktop applications.
a. In some cases, users see the Seclore’s buffer file when they open a protected file on their desktop. The buffer file contains the enterprise’s logo and a customized URL of a webpage that helps users with ways to open the protected file.
b. To enable faster deployment of the Policy Server for new Seclore customers, we’ve removed the enterprise logo from the buffer file and added a generic URL of a file opening app that will help users open the protected file.
c. Buffer files for existing Seclore customers will remain unaffected.
7. Fixed the issue where copies of edited files wouldn’t get sent to the user.
a. Before the fix: Users wouldn’t receive their copies of files edited online. This issue was observed in Seclore 3.16.1.0 and later versions.
b. After the fix: This issue is now resolved.
8. Fixed the issue where an email notification wouldn’t get sent to users after they reset their Seclore password.
9. Fixed the issue where Seclore-protected files wouldn’t open in Seclore Online in certain rare scenarios.
a. Before the fix: Seclore-protected files wouldn’t open in Seclore Online when opened from SharePoint On-Premises 2019. This issue was observed in Policy Server 3.10.3.0 with Seclore 3.16.1.0.
b. After the fix: This issue is now resolved.
10. Fixed the issue where edits made to a protected file online wouldn’t get saved back in certain scenarios.
a. Before the fix: Edits made to a protected file 15 minutes after it’s opened online wouldn’t get saved back. This issue was observed in Policy Server 3.10.1.0 with Seclore 3.16.1.0 and later versions.
Product Management Team
1. Introducing two-factor authentication (2FA) with Time-based One-time Password (TOTP) for Seclore FIM.
a. Enterprises can now enable two-factor authentication for internal users and external collaborators and partners.
b. Users would be prompted to register their TOTP app when they try to log in for the first time after 2FA is enabled for an enterprise. Any TOTP app can be used for this purpose.
c. Users would then be prompted to enter the code generated by their authenticator app as a second factor of authentication every time they try to log in.
d. 2FA can be enabled by System Administrators from the Repositories section of the System Administrator portal.
2. Introducing support for OpenID Connect.
a. Enterprises can now enable user authentication with any authentication provider that supports OpenID Connect protocol.
b. Apart from the Google and Microsoft authentication options available earlier, enterprises can set up other authentication providers like Okta, PingFederate, other out-of-the-box or custom applications that support OpenID Connect.
3. Enterprises can now choose to disable the default log-in fields (Email ID and Password fields shown by Seclore) and only show the third-party authentication options such as Google, Microsoft, or any other supported authentication provider.
4. Enterprises can now enable user authentication in Seclore FIM with only email-based one-time passwords (OTP).
a. This feature can be enabled by System Administrators in the ‘Repository Details’ section in the ‘Repositories’ tab.
b. Once it’s enabled, new users wouldn’t get an option set a password. They’ll receive an OTP on email every time they try to log in.
5. Activities performed by enterprise applications will be logged in the Policy Server with the enterprise application’s name.
a. During content scanning, enterprise applications may protect, unprotect, or share files. Such activities will now be logged in the Policy Server with the enterprise application’s name, unlike earlier, when it was logged with the file owner’s name.
b. Only System Administrators will be able to see the logs of activities performed by enterprise applications.
c. The file access summary sent daily to file owners won’t contain the activities performed by enterprise applications.
6. Made changes to the buffer file for desktop applications.
a. In some cases, users see the Seclore’s buffer file when they open a protected file on their desktop. The buffer file contains the enterprise’s logo and a customized URL of a webpage that helps users with ways to open the protected file.
b. To enable faster deployment of the Policy Server for new Seclore customers, we’ve removed the enterprise logo from the buffer file and added a generic URL of a file opening app that will help users open the protected file.
c. Buffer files for existing Seclore customers will remain unaffected.
7. Fixed the issue where copies of edited files wouldn’t get sent to the user.
a. Before the fix: Users wouldn’t receive their copies of files edited online. This issue was observed in Seclore 3.16.1.0 and later versions.
b. After the fix: This issue is now resolved.
8. Fixed the issue where an email notification wouldn’t get sent to users after they reset their Seclore password.
9. Fixed the issue where Seclore-protected files wouldn’t open in Seclore Online in certain rare scenarios.
a. Before the fix: Seclore-protected files wouldn’t open in Seclore Online when opened from SharePoint On-Premises 2019. This issue was observed in Policy Server 3.10.3.0 with Seclore 3.16.1.0.
b. After the fix: This issue is now resolved.
10. Fixed the issue where edits made to a protected file online wouldn’t get saved back in certain scenarios.
a. Before the fix: Edits made to a protected file 15 minutes after it’s opened online wouldn’t get saved back. This issue was observed in Policy Server 3.10.1.0 with Seclore 3.16.1.0 and later versions.
b. After the fix: This issue is now resolved.