Maintenance Notice - PDF Generation
Dynamic PDF generation for web-based content is temporarily unavailable. This maintenance affects dynamic PDF files that are generated from either the HTML-based page or manual that you are viewing. Links that normally allow this functionality have been hidden, and will reappear as soon as the feature is restored.

Note: Access to static files, including PDF files that are not dynamically generated from our web-based content, is unaffected.

Jump to: navigation, search

Gplus Adapter with Salesforce Single sign-on (SSO) identity provider

You can simplify your agent log in process by integrating Gplus Adapter with Salesforce to use Salesforce as your single sign-on (SSO) identity provider (IDP). This means that your agent only has to provide their Username and Tenant to log in to Gplus Adapter after they have logged into Salesforce using Salesforce as your SSO identity provider.

Follow these steps to set up SSO with Salesforce as the identity provider:

  1. Enable Salesforce as an Identity Provider
  2. Define Gplus Adapter as a Connected App in Salesforce

Enable Salesforce as an Identity Provider


  • You must have an Admin role in your organization's Salesforce account
  • User email address (username) that you use to login to Salesforce. Note: Username email addresses must be the same in both Salesforce and Gplus Adapter.

Enable Salesforce as an Identity Provider

  1. Follow the steps in the Enable Salesforce as an Identity Provider article in the Salesforce Help.
  2. In the Identity Provider view, click Download Metadata to obtain a copy of the IDP metadata XML.

Enable SSO on Genesys tenants

  1. Employing SAML for SSO requires two parts, a Service Provider (Genesys Auth Service) and an Identity Provider (Salesforce). To complete your Service Provider configuration, you must upload the Salesforce Identity Provider IDP-metadata XML file you created in the previous procedure to Agent Setup (refer to the Agent Setup SSO article).
  2. Download and open the SP-Metadata XML file in an XML viewer and find the Location parameter. You will need this parameter for the Entity ID and the ACS URL when you define Gplus Adapter as a Connected App in Salesforce. The Location URL looks something like this:<string representing the Entity ID>.
  3. Contact your Genesys representative to enable the settings that are related to logout under SSO.

Define Gplus Adapter as a Connected App in Salesforce

  1. To configure a new Connected App follow the instructions in the Salesforce Help Defining Service Providers as SAML-Enabled Connected Apps document.
  2. Specify the required fields under Basic Information:
    • Connected App Name (for example, Gplus Adapter)
    • API Name (for example, GWS)
    • Contact email (the email address of the Admin user)
  3. Under Web App Settings, select Enable SAML
  4. Use the Location string from the SP-Metadata xml file of the Enable Salesforce as an Identity Provider procedure to provide Entity ID and ACS URL:
    • Entity ID: The long string of numbers and letters at the end of the Location parameter URL after the last "/".
    • ACS URL: The URL from the Location parameter that you obtained from the SP-Metadata in step 2 of the Enable SSO on Genesys tenants procedure.

    Gplus 900 Salesforce Setup New Connected App View.png

  5. Use the identity provider event log to troubleshoot errors when trying to log in to Gplus Adapter.

Agent SSO login workflow

This is the general workflow when Gplus Adapter initiates the login process and uses Salesforce to identify the user:

  1. An agent logs in to Salesforce.
  2. The agent provides their Username and Tenant name in Gplus Adapter and clicks Next.
  3. GPlus Adapter sends a request to Salesforce to authenticate the user.
  4. Salesforce identifies the agent specified in the request and sends an authentication response.
  5. Gplus Adapter authenticates the response sent by Salesforce.
  6. If the agent is authenticated, they are logged in to Gplus Adapter while logged in to Salesforce.

Useful links

This page was last edited on October 30, 2019, at 16:35.


Comment on this article:

blog comments powered by Disqus