iMIS + eventScribe/Survey Magnet Single Sign-on

Overview

The eventScribe single sign-on (SSO) option is available for registrants. 

Description

The user account originates in the membership system and that system remains the source of truth. A user must have an account in the third-party system to log in. The option to create an account or import users in eventScribe is not available when there is an SSO. The create account option should exist on your third-party system's login page.

We can restrict access based off registration package. Read the article, eventScribe - Registration & Access Grid Instructions, for details. 

Registrant Experience

• User starts on the website or mobile app homepage
• User clicks 'Login' button and is redirected to the third-party system's login page to enter their login credentials
• The third-party system verifies the login credentials and passes eventScribe an authentication token
• eventScribe checks against the registration API for the most current information to confirm the user should be able to log in
  • If authentication is successful, the user is redirected back to website or mobile app homepage
  • If authentication is unsuccessful, a unique error message will display depending on the type of error
  • If the user is not registered, the user will see "You are not registered for this event."
• If it's the first time the user has logged in, a user account is created in eventScribe
• If the user has logged in previously, their registration package and profile fields will be updated, if applicable
  • Mobile app does not force users to log out so typically once a user has logged in, they stay logged in

Considerations & Expectations

• The registration system is the source of truth; all users must originate in the third-party system
• Communication about login instructions should be sent from the registration system (i.e. registration confirmation email, know-before-you-go email) 
• Clients are expected to provide test accounts for each access scenario (i.e. access levels, unlock codes, etc.) and to thoroughly test the integration; this is how you will know the integration is working as expected 
• It is encouraged to launch your website login integration and promote schedule building approximately a month before your event so if there are any issues, they can be addressed prior to the event start date
  • Mobile app launch is based on your contract (pro = 1 month out, standard = 2 weeks out) 
• Client is expected to update their website and/ mobile app with customer service instructions for their end-users. Read the article, eventScribe Integration - Login & Customer Support Instructions, for recommendations
• Cadmium technical support is meant for technical questions about the platform. Clients are expected to assign someone from their team/registration company to field end-user questions about registration, access, and login credentials 

Survey Magnet

You typically do not need a login integration with Survey Magnet directly unless it's standalone, meaning you have not contracted the eventScribe website or mobile app. If you have the website and/or mobile app, the integration point is with eventScribe. You'll add a link to the Survey Magnet in your website and/or mobile app navigation menu. When the user clicks the link, the user data automatically syncs between the products. 

The exception is if you only have one eventScribe product - website OR mobile app - and you want users to be able to get from a third-party software directly into Magnet. For example, if you are NOT using our mobile app and you want users to be able to go from your third-party app into the Magnet directly, you would need to add-on a direct Magnet SSO. 

Note, Survey Magnet can only accommodate one unlock code per presentation evaluation, so if you have a complex registration structure, we will have to discuss the requirements to ensure we can accommodate your needs.

Troubleshooting

The client should submit a ticket to integrationservices@gocadmium.com with username/password and error message. For security, you should request the user temporarily reset their password to ‘Test123’, so they don’t have to provide their actual password.

Required Credentials

We need the following for all integrations (repeat or new):

• Custom based on type of iMIS integration - ask your integration services project manager

If new, we also need:

• Client secret 
• Client ID 
• SSO URL
• API endpoint

Field Mapping

The following fields are mapped from iMIS to eventScribe. Fields are updated upon login.