2.2 Requirements

Use the information in the following table to verify that you meet the requirements for CloudAccess before deploying the appliance.

Table 2-1 CloudAccess Requirements

Components

Requirements

VMware

One of the following versions of VMware:

  • vSphere Hypervisor 5.0

  • vSphere 5.0

  • ESXi 4.1

  • ESX 4.1

Node

Minimum hardware requirements for each appliance node in the cluster:

  • 60 GB disk space

  • 2 Cores

  • 8 GB RAM

Cluster

Supported cluster configuration:

  • Up to a five-node cluster

  • Each node must reside in the same IP subnet

Browsers

Administration: Supported browsers for administration tasks:

  • Firefox 19 and 20 on Windows 7

  • Google Chrome 25 and 26 on Windows 7

  • Internet Explorer 9 and 10 on Windows 7

Users: Supported browsers for users:

  • Firefox 19 and 20 on Windows 7

  • Internet Explorer 9 and 10 on Windows 7

  • Google Chrome 25 and 26 on Windows 7

  • Safari 5 on Windows 7

Mobile Devices

Administration: Not supported on mobile devices.

Users: Supported mobile devices for users:

  • iPhone with iOS 6.x

  • iPad with iOS 6.x

Email Clients

Supported email clients for the email proxy:

  • Windows Live Mail 2011

  • Latest version of Apple Mail Client on iPad or iPhone with iOS 6.x

DNS

CloudAccess requires that all appliance nodes, administration workstations, end-user workstations, and identity sources be able to resolve the public DNS name of the appliance.

SaaS Application Requirements

Each SaaS application has different requirements. To see the requirements for each SaaS application, see the Section 4.0, Configuring Connectors.

Active Directory

Verify that your Active Directory environment meets the following requirements:

  • Only Windows Server 2008 R2.

  • A unique identity for each user account, whether you have one or more domains. CloudAccess uses the sAMAccountName as the unique identifier for the users.

  • All of the following required Active Directory attributes populated on the Active Directory users:

    • First name

    • Last name

    • Full name (Display name is the field that populates this attribute.)

    • sAMAccountName or Logon Name (Pre-Windows 2000)

    • User Principal Name (UPN)

    • Email address

    For more information, see Section 3.5.1, Active Directory Mandatory Attributes.

Obtain the following required items:

  • The password and the fully distinguished LDAP-formatted name of a user in Active Directory that has read access to the user objects. This user makes LDAP binds to Active Directory.

  • The name and password of a user in Active Directory that becomes the administrator of the appliance. The user must reside in the search context of the domains.

  • The IP address of one or more Active Directory servers that contain the users.

  • The context of the users in Active Directory.

eDirectory

Verify that your eDirectory environment meets the following requirements:

  • eDirectory 8.8.7 or eDirectory 8.8.6.

  • All of the following required eDirectory attributes populated on the eDirectory users:

    • CN (Username is the field that populates this attribute.)

    • Given Name (First name is the field that populates this attribute.)

    • Internet EMail Address

    • Surname (Last name is the field that populates this attribute.)

    For more information, see Section 3.5.2, eDirectory Mandatory Attributes.

Obtain the following required items:

  • The password and fully distinguished LDAP-formatted name of a user in eDirectory that has the following rights:

    • Property Rights

      • CN: compare, read, inherit

      • Description: compare, read, inherit

      • Given Name: compare, read, inherit

      • GUID: compare, read, inherit

      • Internet EMail Address: compare, read, inherit

      • Login Disabled: compare, read, inherit

      • Member: compare, read, inherit

      • Group Membership: compare, read, inherit

      • Surname: compare, read, inherit

    • Entry Rights: browse, inherit

  • The name and password of a user in eDirectory that becomes the administrator of the appliance. The user must reside in the subtree of the search context for the identity source specified during the initialization of the appliance.

  • The IP address of one or more eDirectory servers that contain a replica of the partition holding the user objects and that run NLDAP.

  • The context of the users in eDirectory.