Zimbra Social can be configured to handle membership in one of two ways:
Define your own membership rules within the community with users authenticated through the standard ASP.NET Forms authentication.
Use the security that is already part of another application in your environment for login, logout, and registration. This enables members of your community to log in once and gain access to all related systems without being prompted to log in or register multiple times. We offer five options for single sign-on authentication:
- Cookie authentication - Shared authentication with applications that don't use Microsoft ASP.NET (e.g.,PHP, ColdFusion)
- Forms authentication - Shared authentication with other Microsoft ASP.NET applications
- Windows authentication - Shared authentication within an internal environment using Windows Active Directory
- Oauth Providers - Shared authentication with an OAuth provider like Facebook or Twitter.
- Zimbra Social OAuth Service - Create an OAuth application for logging into Zimbra Social from your website. This works well if you are utilizing Core Services on your site.
- Oauth Providers - What OAuth is, sample code for creating a custom OAuth client, and best practices.
- How to configure Zimbra Social for OAuth client applications - How to set up an OAuth client in the Control Panel.
- How to create an Evolution OAuth app - Code examples for authorizing the application and handling the OAuth response.