How SSO Works in Salesforce

A user can be authenticated to various Glance services, either on the web or via the clients using a Login Key.

Authentication requires a Glance PartnerId (Group ID), a PartnerUserId (PUID) that identifies the User within the Group, and a LoginKey. All three are passed on a web page URL or a custom protocol URL invoking the client.

Glance for Salesforce generates a LoginKey using the API Key provisioned in the customer Org Custom Settings, the PartnerUserId (from the specified Salesforce User field) and the GroupId of the default admin user.

Glance for Salesforce then passes the LoginKey, PartnerId, PartnerUserId to Glance.

For web agents these are passed on the Cobrowse join URL. See the Single Sign-On section under Joining a Session Through CRM Integration in the Glance Cobrowse Setup Guide.

For agents using the Glance Client (formerly Panorama), the LoginKey and other parameters are passed to the client on the glancepanorama://… protocol URL.

Flow Diagram

An example of the salesforce sso flow

Detailed Flow

  1. The agent browser requests object (Lead, Contact, Case) from Salesforce. The Salesforce serves a page layout with an embedded Glance for Salesforce Visualforce page.
  2. The browser requests the Glance for Salesforce Visualforce page.
    • The Glance for Salesforce Apex code retrieves the PartnerId (GroupId) from Company Settings, PartnerUserId from specified User field, and shared secret APIKey from Custom Settings.
    • Generates the LoginKey and glancepanorama:// protocol URL.
    • Responds with page containing buttons, Javascript and URL.
  3. The agent clicks the Glance button.
    • The Javascript invokes a protocol URL.
    • The registered protocol handler (GlanceLauncher.exe) opens with a URL containing command and parameters: PartnerId, PartnerUserId, LoginKey.
  4. The protocol handler .exe file launches the Glance Client (if not running), then transmits protocol URL (via ServiceModel/named pipes).
  5. The client calls Glance Web Services to authenticate, passing the PartnerId, PartnerUserId and LoginKey.
  6. Web Services uses PartnerId to retrieve secret APIKey, and validates LoginKey. Then maps the PartnerUserId to a Glance user, and validates access and privileges. The web service returns validation, privileges and settings and for actions that start a session return a server and server key.

By continuing to use the site, you agree to the use of cookies. Learn More