Gigya Job Openings

Page History

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Field Mapping

Fields in one database are dynamically mapped to the corresponding field in the other database. For examples, see Gigya Connector for Drupal 8Gigya Extension for Magento 2.0, and Gigya Connector for Sitefinity 9

By default, the GConnector usually maps the following fields for every user in every CMS: first namelast name, and email

Hooks

GConnectors usually offer the option of registering to specific events and adding custom code. Gconnectors offer hooks that are fired after the following events:

  • Field mapping: A common use case is transforming the user's birthday from 3 Gigya fields (profile.birthDayprofile.birthMonthprofile.birthYear)  into one CMS field (e.g., birthDate).
  • Language: Enables making on-the-fly exceptions to the GConnector language settings and loading screen-sets in different languages.
  • Screen-sets: Passes into the screen-set specific values  for the parameters of accounts.showScreenSet
  • Global parameters: Enables overriding the global parameters defined for the GConnector, as needed. 

Security

Gigya is committed to maintaining the highest level of security. Our platform is designed to protect customer data with a series of strict security and compliance standards which are applied to our GConnectors as well. These include the following principles: 

  • The Application Secret is never used or stored in the CMS (session /cache/cookie etc.), but rather loaded from the database for each call. 
  • The Application Secret is encrypted in the database. 
  • Validates using accounts.exchangeUIDSignature
  • Gigya's Web SDK is loaded over HTTPS. 
  • Session expires automatically. 
  • Uses server-side calls when verified user data is required.
  • Server-side calls are signed.

Configuration Options

Generally, the GConnector configuration options (sometimes available within the CMS Admin area) align with those of Gigya's Global Configuration. In addition, they include

  • Field mapping 
  • Session management and session expiration settings. See Managing Session Expiration for more information about Gigya's session management. 
  • Redirect and logout URLs

Multi-Site and SSO Support

GConnectors support multi-site implementations. Configuration for each site is independent, and in some cases sites can inherit configurations from a master site. In addition, SSO is supported by Gigya. For more information, see Site Groups and Single Sign-On 

When configuring an SSO segment, the session management of all sites in the segment should share the same definition: 

  • Dynamic: This is the best practice configuration for SSO. When all sites in the segment are set to dynamic session management, the session is restarted with every call to the server. The best practice is to set the session duration to the same length for all sites that share an SSO segment. 
  • Fixed: when all sites in the segment are set to fixed session management, the start of the session is counted from the first site to which the user logged in.

Consent

For customers who implement Gigya's Consent Management, enables syncing the user's consent status to a consent object or custom field in the target platform. Connectors who have this feature can dynamically call any Gigya screen during the various customer interactions with their site. 

This is supported for the following GConnectors: 

  • SAP Commerce Cloud
  • Magento 2

Lite Screen-Set

Support showing the Lite Registration screen-set, for registering passwordless users via the connector integration. Lite registrations is used for newsletter subscriptions, lead generation and other customer communication use cases. The information is saved to Gigya's database. 

This is supported for the following GConnectors: 

  • SAP Commerce Cloud
  • Magento 2

GConnector Data Flow

The following diagram illustrates the typical data flow between Gigya (RaaS accounts namespace and Data Store) and the CMS (both client and server side), using the GConnector extension of the CMS. 

  • The Accounts namespace is where core Gigya user and identity data is stored, and includes the basic identifiers such as first and last name, email, UID and any other fields stored in the profile and data objects.
  • Gigya's Data Store (DS) is a premium product, an additional database with a flexible, dynamic schema. The DS part of the flow below is relevant only to customers who have implemented the Data Store.

For a list of links to the APIs participating in this flow and other relevant documentation, see below. 

Note

This flow is relevant both to implementations that use Gigya's Screen-Sets and custom screens with Gigya's Web SDK.

Sequencediagram
divIDgConnectorSequence
participant CMS Client Side
participant CMS Server Side
participant Gigya
participant DS
Note over CMS Client Side: User clicks "Login"
CMS Client Side->Gigya: accounts.login
Gigya-->CMS Client Side:onLogin event
CMS Client Side->CMS Server Side: AJAX request to handle CMS login \n with UID, signature and timestamp
CMS Server Side->Gigya: accounts.exchangeUIDSignature
Gigya-->CMS Server Side: User signature
CMS Server Side->CMS Server Side: Validate user
CMS Server Side->Gigya: accounts.getAccountInfo
Gigya-->CMS Server Side: User object 
Note over DS: Optional
CMS Server Side->DS: Get DS info \n (triggered by post getAccountInfo hook)
DS--> CMS Server Side: DS info \n Fires post ds.get hook
Note over CMS Server Side: Post merge hook
Note over CMS Server Side: Field mapping \n (Data transformation)
Note over CMS Server Side: Custom field mapping using hook
CMS Server Side->CMS Server Side: Create user/update existing user
CMS Server Side-->CMS Client Side: User is logged in to Gigya and CMS

APIs and Objects Used in GConnectors

...

      
CMSData Store SyncBack Office (Bi-Directional) SyncUID-Based SyncGigya-Led Session ManagementUser DeletionLite Screen SetUser Consent
AEM      
Yes
Yes
Drupal 7
Yes
 
Yes
Yes
Yes
  
Drupal 8
Yes
 
Yes
Yes
Yes
Yes
Yes
SAP Commerce Cloud
Yes
Yes
Yes
  
Yes
Yes
Magento 1
Yes
Yes
Yes
Yes
   
Magento 2
Yes
Yes
Yes
Yes
Yes
Yes
Yes
Salesforce Commerce Cloud      
Yes
Yes
Sitecore  
Yes
Yes
   
Sitefinity
Yes
 
Yes
Yes
Yes
  
Umbraco
Yes
 
Yes
Yes
   
Wordpress  
Yes
 
Yes
Yes
Yes

 

Product Updates

You can view the change log of the following GConnectors: 

...