Installing and configuring Sitecore itself is beyond the scope of this documentation. This document also assumes that the implementer is familiar with Sitecore general usage and configuration. For more information on Installing and Configuring Sitecore, please refer to the Sitecore documentation.
Enable the plugin
Setup the OAuth client
userSynchronizationCookieName = "EvolutionSync"
evolutionUserCreationManagementUserName = "admin"
generateSitecoreUrls = "false"
oauthCallbackHandler = "~/sitecore%20modules/shell/telligent/h/oauth.ashx"
themeUrl = "/sitecore%20modules/shell/telligent/a/css/screen.css"
modalThemeUrl = "/sitecore%20modules/shell/telligent/a/css/modal.css"
userResolver ="Telligent.Evolution.Extensions.Extensibility.Version1.SitecoreConnect.Authentication.SitecoreUserResolver, Telligent.Evolution.Extensions.SitecoreConnect"
loginUrl = "~/login.aspx"
logoutUrl = ""
Zimbra Connect for Sitecore relies on being able to inject information into the <head /> element of a web page. To do this, ensure that your master layout or wherever the <head /> is defined has the following attribute: runat="server". Example: <head runat="server">...</head>.
Zimbra Connect for Sitecore offers two methods of authentication. The first ties into an existing authentication mechanism in Sitecore; the second allows authentication to be handled by Zimbra Community.
This mode assumes you have an existing authentication system in Sitecore and that users are stored in Sitecore, meaning the authenticated user can be accessed via Sitecore.Context.User. In this method, Zimbra Connect will ask Sitecore.Context.User for an authenticated user and use that username to find a user in your Zimbra community. It also handles creating the user if the user doesn't exist.
Setting up in Zimbra Community
It is important to note that in order for Zimbra Connect for Sitecore to create a user, the following conditions must be met:
Setting up Sitecore
While many features are available out of the box, with this configuration there is still an expectation that work will or has occurred beyond the scope of Zimbra Connect for Sitecore. This includes, but is not limited to, building a user management and authentication process in Sitecore and depending on the features of Zimbra Connect you wish to use, additional code to that process.
This process stores and authenticates users in Zimbra Community directly. It assumes there is no user management or authentication process in Sitecore at all aside from what is used for management of the software. Logging into Sitecore has no effect on the authenticated state of Zimbra Connect for Sitecore.
Setting up Zimbra Community
Beyond initial setup, there are no additional steps for Zimbra Community. Ensure that the OAuth client was set up as directed with Authorization code and Trusted client selected in the grants area.
You can choose to enable Single Sign On in the connector. This is accomplished using a sync cookie that Zimbra Community creates and reads to determine who is logged in (or not) in Sitecore.
This option requires the Sitecore site and Zimbra Community to be on the same parent domain.
Zimbra Community setup
Powered by Zimbra