Eventscribe Expo Harvester Single Sign-on (SSO)

Below is an overview of the Expo Harvester SSO integration we offer through Cadmium Eventscribe Integration Services.  

Description

An SSO requires a user to have an account in the client’s AMS or CRM and to be associated with a company record. The AMS or CRM acts as the third-party identity provider and source of truth for information about the company and user.

Steps:

1. User initiates login through a Cadmium link or rental process landing page
2. User is redirected to the third-party identity provider to authenticate 
3. Third-party identity provider redirects the user back to Expo Harvester
4. Expo Harvester creates a company and user record (mapping data from the identity provider) in the background and logs the user in
5. Through custom code, we can accommodate triggering member and non-member pricing based on an identifier in the AMS/CRM profile such as (i.e. member type, company type, etc.).

Field Mapping (Individual Booth Admin)

Expo Harvester uses field mapping to associate user data received from the Identity Provider (IdP) with corresponding booth admin profile fields. The fields listed below represent Cadmium’s standard SSO field mappings. Actual field availability and naming may vary by IdP.

• member_id (required)
• member_status (Active or Non-Member)
• first_name (required)
• middle_name 
• last_name (required)
• prefix 
• suffix 
• credentials 
• pronouns
• organization_position
• organization 
• email (required)
• phone_work 
• phone_mobile 
• address1 
• address2 
• address3 
• city 
• state 
• postal_code 
• country_code

Field Mapping (Company)

Expo Harvester uses field mapping to associate company data received from the Identity Provider (IdP) with corresponding company profile fields. The fields listed below represent Cadmium’s standard SSO field mappings. Actual field availability and naming may vary by IdP.

• company_member_ID (required)
• company_name (required) 
• company_email
• company_phone
• company_address1
• company_address2
• company_address3
• company_city
• company_state
• company_postal_code
• company_country_code

Considerations

• It is required that the AMS/CRM is set up as a parent-child relationship between company and user. 
• If you plan to import users and/or company information AND offer a single sign-on, you must ensure that those booth staff users have a Member ID and that the company with which they are associated has a Company ID. This is required for the SSO to validate against. Otherwise, the SSO will say 'user not found'. 
• If you are considering single sign-on with Expo Harvester, we should do a discovery call to discuss your AMS/CRM setup to ensure we can meet your expectations.