14.2 Requirements for the Single Sign-on Connectors

Use the information in the following table to gather connector-specific requirements.

Table 14-1 Connector Specific Requirements

Connector

Requirements

Connector for Accellion (SAML 2.0)

  • An enterprise Accellion account.

  • The Accellion domain name and the application ID. The Accellion administrative URL contains both elements.

    http://domain_name.accellion.net/courier/application_id/index.html

  • The administration link in Accellion to configure Single Sign-On (SSO).

Connector for ADFS (SAML 2.0 or WS-Federation)

  • An ADFS 2.0 system

  • The metadata file from the ADFS 2.0 system.

    https://adfsserver/FederationMetadata/2007-06/FederationMetadata.xml

Connector for Azure (WS-Federation)

  • An Azure account.

  • A Windows Azure Access Control Service.

    For more information, see How to Authenticate Web Users with Windows Azure Access Control Service.

  • The Metadata from the Windows Azure Access Control Service.

  • If the you configured the connector for Office 365 in the same domain, ensure that you configure WS-Federation as the federation protocol for the connector for Office 365.

Connector for Box (SAML 2.0)

  • An enterprise level Box account. Obtaining an enterprise Box account requires you to provide configuration details for your organization so Box can help set up the SSO connection.

Connector for Jive (SAML 2.0)

  • A Jive account.

    NOTE:There are three types of Jive accounts: Cloud, Hosted, or On Prem. If you have a Hosted or On Prem account, you have access to the federation settings required to configure the connector for Jive. If you have a Cloud account, you must contact Jive technical support to configure the federation between Jive and CloudAccess.

  • The base metadata URL from your Jive instance.

Connector for ServiceNow (SAML 2.0)

  • A management ServiceNow account created with the SAML 2.0 Update 1 plugin.

  • The ServiceNow instance name. For example, http://you_instance.service-now.com/.

Connector for VMware vCloud (SAML 2.0)

  • A VMware vCloud deployment with a vCloud director and the following information from your vCloud director:

    • DestinationURL

    • vCloud Host IP address

    • Organization

Connector for WebEx (SAML 2.0)

  • A WebEx account. Trial accounts do not support federation.

Connector for Zoho (SAML 2.0)

  • A Zoho business account.

  • A valid public domain that you have registered with Zoho. Select the Enable MailHosting option after logging in to the Zoho account.