Query-to-Authenticate - 2023 Update

Starting in 2023, query-to-authenticate integrations will no longer include a pull of all registrant data. Previously, we've pulled in users in addition to authenticating upon login. The one exception is if you are using Cadmium's lead retrieval product. Please let us know if that's the case. 

Functionality

The query-to-authenticate login integration will function as follows:

• User clicks 'Login' on the eventScribe site (website/app), is directed to the login page, and enters 'Registration Email' and 'Registration ID'
• The integration will check against the registration API for the most current information to confirm the user should be able to log in
  • If yes, and the user is logging in for the first time, the account will be created in eventScribe
  • If yes, and the account exists, the profile will be updated, if applicable
  • If no, the user will receive a message that says "You are not registered for this event."

Reasoning

In support of our 2023 goals to increase efficiency and reliability of integrations, we have made this decision for the following reasons: 

• Most important, it's not necessary to do both a pull and login integration. We authenticate users upon login and pull over their most current registration information at that time 
• The pull runs on a schedule so the data is never current; the login integration pulls in the most current information upon login 
• Doing both a pull and a login authentication causes confusion for clients in terms of functionality
• We have to maintain two separate code files which leads to errors, duplicate work, and inefficiency
• A pull is often not reliable. If we are trying to pull a large quantity of users, the request to the third-party system may time-out because it's too taxing
• Single sign-on integrations (which make up the majority of our projects) already follow this approach so this will standardize our offering 

Impact

The following items will not change: 

• The registration system will remain the source of truth 
• All users must originate in the registration 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 start date. Mobile app launch is based on your contract (pro = 1 month out, standard = 2 weeks out)
• 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 
• Integration issues should be reported by the client to integrationservices@gocadmium.com after confirming the user should be able to log in and that there is in fact an issue. Please provide the user's registration email and registration ID

Changes include:

• Users will be added to the eventScribe user list the first time they log in
• Cadmium will not know users' login information until they've already logged in