For successful configuration of SAML SSO, an identity provider that complies with the SAML 2.0 standard is a prerequisite.
This article provides basic information regarding SAML identity providers' use.
Jive can be integrated with a wide variety of SAML IdPs. Following are the two commonly used IdPs used with Jive.
Commonly used IdPs
Jive regularly tests SAML support with the following IdP:
ADFS (Active Directory Federation Services) is the most common SSO provider used by Jive customers. For more information, see Active Directory Federation Services at the Microsoft portal.
We can typically assist with the configuration for these providers. Troubleshooting assistance for other IdP integrations is available through Jive Professional Services.
Configuring IdPs for SSO
Certain IdPs require special configuration before you can set up SAML SSO. We do not provide a complete description of required IdP configuration for your identity provider. The following list describes some known configuration prerequisites for specific IdPs.
Prerequisite: Set the expected digital signature to
ADFS expects the digital signature to be
SHA-256, but Jive sends it as
SHA-1. To change this expectation, go to the Advanced tab of your Relying Party Trusts profile and set the secure hash algorithm to SHA-1.
Prerequisite: Use the Jive
entityID as the Siteminder profile name.
Typically, the Jive
entityID, which is set by using the Base metadata URL in the Advanced tab of your SAML SSO settings, is the same as the