How do I integrate with eShow registration to set up authentication (app login)?

You can integrate the EventPilot platform with eShow registration so attendees log in with their badge ID and last name. Once eShow authentication is set up, attendees enter their badge ID in the username field and their last name in the password field.

Before you begin

1. Register a test attendee for your event.
2. Have the test attendee's badge ID and last name ready for login testing.
3. Ask eShow for the API Token for your event.
4. Confirm with eShow that API access has been enabled for your event.
5. Confirm the eShow API prefix for your event. Most events use s4.
6. If specific registration types should not be allowed to log in, ask eShow for the exact ROLE_TYPE values.

Email to send to eShow

You can send this request to your eShow contact:

I am using the EventPilot platform for my event and would like to set up authentication integration using the badge ID and last name combination as the login.

Could you please provide the API Token for my event?

Please confirm that API access has been enabled.

Please also confirm the API prefix for my event. If we need to prevent specific registration types from logging in, please provide the exact ROLE_TYPE values.

Set up eShow authentication in Auth Settings

1. In Conference App Builder, go to Settings > Auth Settings.
2. In Authentication Type, select Registration Provider Eshow API (badge ID and last name).
3. If a warning appears about changing authentication, review it before continuing. Changing authentication after users have already logged in can affect login, sync, and user data.
4. On the Setup step, enter the values below.

Setup step

1. In Enter the API Token, paste the API token provided by eShow.
2. In API Prefix (optional), leave s4 unless eShow or ATIV gives you a different API prefix.
3. In Excluded Reg Types (optional), leave the field blank unless some eShow registration types should not be allowed to log in. If exclusions are needed, enter the exact ROLE_TYPE values from eShow separated by commas, for example EXH,GUEST.
4. Leave Data Forwarding turned off unless ATIV specifically instructs you to turn it on.
5. In Display Registration URL (optional), enter the full registration URL if you want attendees to see a registration link. The URL must include https://.
6. In Test Username, enter the badge ID for your test attendee.
7. In Test Password, enter the test attendee's last name.
8. Turn on Users must log in at startup only if attendees must log in before they can access the event. Leave it off if login is only needed for personalized features.
9. Select Next. The system checks the test login before continuing.

Instructions step

1. In Settings Page, explain why attendees should log in. For example: Log in to sync your schedule and access personalized event features.
2. In Login Instructions (list an email address if a user has problems logging in), tell attendees to use their badge ID and last name. Include the support contact they should use if they cannot log in.
3. In Username Hint Text, enter Badge ID.
4. In Password Hint Text, enter Last Name.
5. Save the authentication setup.

Test before launch

1. Publish the event to proof or test the event in the environment recommended by your project manager.
2. Log in with the test attendee's badge ID and last name.
3. Confirm the attendee can access the expected event content.
4. If you entered excluded registration types, test one attendee who should be allowed to log in and one attendee who should be blocked.
5. After testing is successful, publish the event for attendees.

FAQ

Can eShow authentication exclude specific registration types?

Yes. eShow authentication can exclude specific registration types using the attendee's ROLE_TYPE. Enter the blocked values in Excluded Reg Types (optional), separated by commas. If an attendee's ROLE_TYPE is excluded, they cannot log in.

Why does login say the user could not be found?

The badge ID may have been typed incorrectly, the attendee may not exist in eShow, API access may not be enabled yet, the API Token may be incorrect, or the API Prefix (optional) may not match the event. Confirm the attendee's badge ID in eShow and verify the API details with eShow.

Why does login say the password is invalid?

The last name entered does not match the last name returned by eShow. Ask the attendee to use the last name from their registration or badge. For eShow login, capitalization, spaces, and punctuation are ignored, but the letters in the last name must match.

Why does login say the attendee does not have permission to access the content?

The attendee's ROLE_TYPE may be listed in Excluded Reg Types (optional). Review the excluded values and the attendee's registration type in eShow.

Why does login say the user data could not be found?

eShow did not return all required profile details for the attendee. Confirm that the attendee's eShow record includes first name, last name, and email address.

Can unpaid, canceled, or privacy opt-out registrations cause login errors?

It depends on what eShow returns through the API for your event. If eShow does not return the attendee, or returns incomplete attendee data, EventPilot cannot complete the login. Confirm the attendee's registration status and API visibility with eShow.

What should attendees enter on the login screen?

Attendees should enter their badge ID as the username and their last name as the password.