Understanding SSO with External Login

When you implement single sign-on (SSO) using an external login, users can choose to log in using any of several different authentication providers including Facebook, Google, and OpenID.

External logins are a good choice for public communities because authentication can be passed to a third-party provider. The community user enters credentials on the provider site. The authentication token is then passed back and verified on the Jive side. Community users can log in with any number of different providers and have all their details pre-populated. For sites that support an avatar attribute, avatars are synchronized as well.

An external login implementation can optionally include Facebook Connect authentication. Both OpenID and Facebook Connect use the Attribute Exchange standard for exchanging information, which enables Jive to pull in profile information about new users. After login the user sees a confirmation page and can verify profile information, pick a username (if this information isn't prepopulated from the profile), and proceed to the Jive community.

OpenID with Facebook Authentication

Enabling Facebook authentication requires you to set up an app on the Facebook developer site. You'll need the application id and the application secret to configure single sign-on.