Unified Workspace has always required an LDAP directory service to serve as the primary datastore for the environment. All configuration objects and user data are stored in this underlying directory service. Until now, LUW required this to be the customer’s production Active Directory, eDirectory, or OpenLDAP infrastructure which required schema extensions be made to the directory to enable LUW to create and modify its own objects and attributes.
As of version 6.5, Unified Workspace can now be configured to run its own, local LDAP directory service right from the LUW internal server itself. With a local LDAP directory to serve as its primary datastore, LUW no longer needs to modify a customer’s production directory schema and will store all of its own configuration objects, single sign-on definitions, and application profiles locally.
This local LDAP directory service is built on
Microsoft’s Active Directory Lightweight Directory Services (AD LDS, formerly known as ADAM). The installation and configuration process has been integrated into the Unified Workspace installation wizard for a more streamlined deployment experience.
Once deployed, user and group information, as well as several attributes, can be imported into the local LDAP directory from one or more customer Active Directory domains. This is configured using a new Directory Sync tool integrated into the Unified Workspace webAdmin dashboard.
For more information refer to the
Unified Workspace 6.5 – New Directory Services Architecture Guide* This feature requires a fresh Unified Workspace install and our Professional Services team is available to support