Overview When using Kerberos SSO or LDAP Directory Integration, customers have the option of setting up user filters in Jive to allow only a subset of users to log in. Filtering can be based on profil...
Overview When customers upgrade their hosted/on-premises (HOPS) instances to Jive 9.1 and above, they may face an error logging in with Kerberos Single Sign-On (SSO). The error message in Restart Jive...
Overview This article describes how to resolve the problem where a user's profile information (attributes like title, department, etc.) is not getting synced from Microsoft Azure AD to Jive upon login...
Overview When Jive is set up to sync users through an LDAP system such as Azure Active Directory, if the LDAP system administrator deletes or disables a user account in the LDAP system and then recrea...
Overview Single Sign-On (SSO) allows you to integrate Jive authentication with an external identity provider (IdP). When you implement Single Sign-On (SSO) with SAML 2.0, information for each user is ...
Overview You are experiencing an issue with Single Sign-On (SSO) when trying to log into the Jive site. The specific error message encountered is 'User not found in external identity table.' Despite s...
Overview Some users may encounter an issue when new users fail to federate from your SSO (eg: OneLogin) to Jive. The error message received from indicates an Invalid locale ID _GB. This problem seems ...
Overview Some users may experience an issue where Single Sign-On (SSO) login fails outside of InPrivate mode in the Edge browser. This problem typically occurs when trying to log into a site after upd...