Verify that you meet the following requirements before you import the connector:
An understanding of identity federation using the SAML 2.0 protocol.
For more information about SAML, see the OASIS website.
A Jive account.
Administrator access to your Jive account. An understanding of Jive and its account management tools are presumed.
A Jive user account for each user who wants to authenticate to Jive through the CloudAccess single sign-on service. The connector for Jive does not provision user accounts.
The location in the Jive administration console where you will configure the SAML 2.0 federation for CloudAccess.
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, Jive requires you to contact Jive Technical Support to configure the SAML 2.0 federation between Jive and CloudAccess. Be prepared to provide them the federation configuration details for your organization at that time.
When you configure the connector, the Federation Instructions provide the information that you (or Jive Technical Support) will need to set up the federation in Jive for CloudAccess. This information includes the metadata; a signing certificate for the appliance; the field values to use; and other guidance.
If you are using a Jive Hosted account or a Jive On Prem account, the Base Metadata URL that is displayed on the SAML 2.0 federation pages on Jive.
If you are using a Jive Cloud account, the Instance name of your account.
(Optional) An X.509 signing certificate from Jive is required to support single logout. Communications use SSL regardless of whether you provide this certificate.
CloudAccess supports one online instance and one offline instance of Jive. Each instance must have a unique Base URL and SAML assertion.