Users within the organization are unable to access any content after joining the community as External Contributors through an invitation. They are logging in to the instance through their federated accounts and able to view the Externally Accessible groups to which they are invited and are able to view listed content through
- The invited users do not have an existing federated user account within the instance.
- But they are able to use the same SSO credentials to sign in after accepting the invitation.
- Such users are able to browse and navigate through externally accessible groups but are unable to view any content.
- This behavior is not observed with other external users who are not part of the organization (& not using SSO).
- Email domains are added to the community domain list to recognize new users going through the registration process and convert as registered users.
Jive Interactive Intranet with SSO enabled.
- Such external users were not allowed to have access to Jive Instance as per the configurations on the IDP. So they were not provisioned with default Jive logins.
- Jive continues to attempt & convert these external users as registered users based on the Community domain list and fails due to IDP restrictions.
- Since the requirement for such users is to only have limited access as external contributors, it is recommended to remove the email domains from Community Domain List.
- This would prevent Jive from forwarding such user registrations to the IDP for validation.
- And these new users can continue to remain as Unfederated External Contributors.
- Once the registration process is completed and the user is able to log in and view all content, their accounts can be converted to Federated accounts.
- This would allow them to use their SSO credentials to log in to Jive but remain as External Contributors.