Voltage SecureMail Mobile Edition Now Supports “Split Domain” Network Architectures
For enterprises that have split domain network configurations, Voltage SecureMail Mobile Edition now allows internal users who are coming from public mobile networks to reach internal Voltage Key Servers. For security reasons, some organizations use a split domain configuration to segregate networks and users.
A split domain network configuration determines which network (including tenants, districts, settings, etc.) can be accessed by which users and/or groups. Most commonly a split domain configuration is used to separate internal and external networks and users. Voltage SecureMail Mobile Edition now supports these configurations. The new capability allows internal mobile users to have access to the internal network to authenticate and download keys to access secure messages when they are using a public mobile network.
- Support for LDAP group lookup for authorization in the Enrollment Service
- TLS 1.1 and 1.2 support for connecting to the Management Console and ZDM/Key Server
- Upgraded Voltage SecureMail to Java 7
- Support for VMware vSphere Hypervisor (ESXi) 5.1
- Support for the latest versions of Internet Explorer (v10), Chrome (v29), Firefox (v23), and Safari (v6) in ZDM
- Support for the latest version of Internet Explorer (v10) and Chrome (v29) in Brand Manager and the Management Console
- Support for Symantec Encryption Desktop 10.3.x for Windows (formerly PGP)
5.0.1 – 5.0.8 Updates
Also included in 5.1 are all of the enhancements made in 5.0.1 through 5.0.8:
- Improved ZDM throughput and resiliency – improved caching of resources
- Active Directory authentication page for Mobile Edition now accepts all username formats: UPN (firstname.lastname@example.org), NT (domainusername), or simple login name (user01)
- Branding of LDAPs authentication page for Voltage SecureMail Mobile Edition
- Copy Sender for ZDM can be set on a per tenant basis
- Native HTML-formatted print option in ZDM
- Admins can now configure the Gateway to use Base64 or Quoted Printable encoding for the Content-Transfer-Encoding of the message_zdm.html, which is required to support Mobile Edition on some Android devices
- CentOS 5.9 upgrade for the Voltage SecureMail Appliance
How Can I Get Help?