This article describes the workflow of how Jive Authentication via Security Assertion Markup Language (SAML)/Single Sign-On (SSO) goes.
SAML is a protocol for exchanging authentication credentials between two parties, a Service Provider (SP) and an Identity Provider (IdP). In this case, Jive plays the role of an SP. The SP sends a request for authentication to the IdP, which then tries to authenticate the user.
The same workflow has also been shown in the flowchart at the end of the article.
- Navigate to your Jive Community.
- If SSO is enabled, you will be redirected to the IdP login page.
- Depending on the configuration of the SSO, the user will either be prompted for the Username/Password or will be logged in automatically.
- Upon successful authentication, the user will be re-routed to the Jive Community.
- While the site loads, Jive will also be syncing the Profile Fields defined in the Attributes Mapping section.
- Once all the profile fields are successfully synced, the user will be able to access the Jive Community and the login process will be completed.