Introducing Domain Based Access for your external users.
Enterprises can now give permissions to recipients of an entire domain while protecting files.
For example, while protecting files using right-click > protect, users can add @stringuard.com in the recipients section. This would give permissions to all users of that domain. Users can also define a policy to give permissions to domains, which can then be used in Hot Folders and integrations.
This feature is useful for external collaboration and lets your partners decide who they wish to share permissions with internally.
System Administrators can disable/enable this feature in any external repository in the Repositories section of the Policy Server portal. They can also add domains (usually public domains like @gmail.com) in the deny list to prevent users from giving access to such domains.
This feature will be enabled by default for all enterprises who upgrade their Policy Server to this version.
Global Security Admins can revoke access for domains. They can also replace or replicate permissions from one domain to another, an individual to a domain, or vice versa.
Changes made to the permissions of a domain will apply to all recipients onboarded using domain-based access.
Recipients who are part of the domain-based access but have also received permissions individually will continue to retain their individual permissions along with domain-based access permissions.
Made improvements to the Policy Server Installation package.
Spring libraries upgraded to version 5.3.18 to address the recently observed Spring4shell vulnerability (CVE-2022-22965).
Product Management Team
Introducing Domain Based Access for your external users.
Made improvements to the Policy Server Installation package.
Spring libraries upgraded to version 5.3.18 to address the recently observed Spring4shell vulnerability (CVE-2022-22965).