By default, Riva for Salesforce is designed to use Standard Impersonation. With Standard Impersonation, Riva for Salesforce
Is "Riva Delegate Authentication - Single Sign-on for Salesforce" still supported? Yes, all of the previous methods are still supported, but the Standard Impersonation model is now the default deployment method for all Riva for Salesforce installations.
Options to Configure Riva to Sync to Multiple Salesforce Users to Exchange
There are two options to configure Riva to sync multiple Salesforce users with Exchange:
This deployment method uses a standard Riva server deployment checklist. When completed, the Riva server includes
Get Started Bundle
Is this the first time you implement Riva On-Premise?
If you need assistance with deploying Riva On-Premise, we offer a Get Started Bundle professional on-boarding service. Within three hours of discovery, installation, configuration, licensing, testing, and introductory admin training, we will have you up and running with Riva On-Premise. To order a Get Started Bundle, contact the Riva Success Team.
These methods are still supported for existing clients. Clients who want to deploy Riva server using hosted or on-premises SSO impersonation methods should book a Getting Started Bundle to ensure that the SSO environment is properly installed and configured.
When to use this Riva configuration option: The hosted SSO provider service enables customers with Riva connections to Exchange Web Services (EWS) on Exchange 2007 or Exchange 2010 or Office 365 to configure Salesforce SSO. This deployment does not require an appointment with a Riva Success Team member.
Limitations: The hosted SSO provider service does not support NTLM / Kerberos authentication. For NTML / Kerberos integration authentication, the on-premises SSO provider must be installed on a server in your data centre.
For the steps to deploy Riva and configure the Riva hosted SSO provider, see Deploy Riva for Exchange and Salesforce using the hosted SSO provider.
Riva clients have the option to deploy an on-premises SSO provider server on a local Windows server hosting a public facing IIS web server. This deployment does require an appointment with a Riva Success Team member to install, configure, and test the local SSO provider service.
When to use this Riva configuration option: This option is available to be used with
For the steps to deploy Riva and prepare to implement the Riva On-Premise DA-SSO provider, see Deploy Riva for Exchange and Salesforce using the on-premises SSO provider.
With this option, the Riva administrator must create a Riva CRM connection for each target user's Salesforce user account and assign a separate Riva sync policy to use the specific CRM connection. If there are five users to sync, the Riva administrator needs to configure five individual CRM connections (one per target user) and five separate sync policies (one per target user). The major disadvantage of this option is that when the user's Salesforce password changes, that password must be updated in the Riva CRM connection for the user.
When to use this Riva configuration option: This option is suitable
For the steps to prepare and deploy Riva for single-user policies, see Deploy Riva for Exchange and Salesforce using single-user sync policies (non-SSO).
Article ID: 611
Last updated: 12 May, 2016