[toc]
Telligent Community Server has a number of OAuth clients that are managed simply by enabling and configuring plugins:
- Facebook authentication
- Google authentication
- LinkedIn authentication
- Live Connect authentication
- Salesforce authentication
- Twitter authentication
Prerequisite
Your Community Server site needs to support SSL in order to comply with the OAuth 2.0 specification. Facebook, LinkedIn, and Twitter providers only support a redirection URL back to the site over SSL. Please see section 10.9 of the IETF spec in order to understand this requirement.
If you don't want to support SSL for either of these providers, you'll need to create a custom OAuth client that overrides one of these providers and has a property for CallbackUrl that doesn't enforce an https callback.
This site can provide assistance for enabling SSL.
Requirement
OAuth clients require that you establish a privacy policy on your site. If you do not create one, you could be in violation of their user policies as well as other possible user issues. Therefore, it's strongly recommended that you create one. You must create your privacy policy using your own legal consultants, and should consider referencing your use of the client. The suggested way of creating a privacy policy statement in Community Server is by creating a site-level content page that you then link within the footer of your site.
Extending OAuth
Developers can extend OAuth support to other OAuth services or even add further functionality to the existing OAuth clients. Click here to read more about it. (The article applies to 7.x, but is still relevant.)