Below is an overview of the Expo Harvester SSO integration we offer through Cadmium Eventscribe Integration Services. We do not offer login integration services for applications or functionality outside what’s listed below.
View the list of supported third-party vendors here.
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:
- User initiates login through a Cadmium link or rental process landing page
- User is redirected to the third-party identity provider to authenticate
- Third-party identity provider redirects the user back to Expo Harvester
- Expo Harvester creates a company and user record (mapping data from the identity provider) in the background and logs the user in
- 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.).
IMPORTANT NOTE
Your AMS or CRM data structure must be set up as a parent (company) with child (user) relationship.
User (Booth Staff Member) Default Fields
The following are our default fields; however, they may vary slightly by third-party application.
- Unique Member ID (required)
- Email (required)
- First name (required)
- Middle name
- Last Name (required)
- Credentials (PhD, MD, etc.)
- Organization
- Title
- Address1
- Address2
- City
- State
- Zip Code
- Country
- Work Phone
- Cell Phone
Company Default Fields
The following are our default fields; however, they may vary slightly by third-party application.
- Unique Company ID (required)
- Company Name (required)
- Address1
- Address2
- City
- State
- Zip Code
- Country
- Telephone
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.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article