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

You can integrate the EventPilot platform with CDS registration so attendees log in with their badge ID and last name. Once CDS 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 your CDS account manager for the Auth Key for your event.
4. Confirm with CDS that the API has been turned on for your event.
5. If specific registration types should not be allowed to log in, ask CDS for the exact registration type values. These are usually the CDS RegClass values.

Email to send to CDS

You can send this request to your CDS account manager:

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 me with the Auth Key for my event?

Please confirm that the API has been turned on.

If we need to prevent specific registration types from logging in, please also provide the exact registration type values and confirm whether they are stored in RegClass.

Set up CDS authentication in Auth Settings

1. In Conference App Builder, go to Settings > Auth Settings.
2. In Authentication Type, select Registration Provider CDS 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 Auth Key, paste the Auth Key provided by CDS.
2. In Excluded Reg Types (optional), leave the field blank unless some CDS registration types should not be allowed to log in. If exclusions are needed, enter the exact values from CDS separated by commas, for example EXH,GUEST.
3. In Field for Reg Type (optional), leave the field blank unless ATIV or CDS tells you to use a different field. The default CDS registration type field is RegClass.
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. Only if users must log in before they can access the event program, turn on Users must log in at startup. 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 and where they can find this information (e.g. registration email). 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, ensure to complete a data publish for attendees.

FAQ

Can CDS authentication exclude specific registration types?

Yes. Use Excluded Reg Types (optional) to block specific CDS registration types from logging in. Enter the exact values from CDS separated by commas. The default field is RegClass. Leave Field for Reg Type (optional) blank unless ATIV or CDS tells you to use a different field.

Why does login say the badge ID was not found?

The badge ID may have been typed incorrectly, the attendee may not exist in CDS, the CDS API may not be enabled yet, or the Auth Key may not be correct. Confirm the attendee's badge ID in CDS and verify that CDS has turned on the API for your event.

Why does login say the username or password is invalid?

The last name entered does not match the last name returned by CDS. Ask the attendee to use the last name from their registration or badge. For CDS 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 registration type may be listed in Excluded Reg Types (optional). If exclusions are configured and the attendee's CDS record does not include a registration type, login may also be blocked. Review the excluded values and the attendee's registration type in CDS.

Why does login say the profile data is incomplete?

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

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

It depends on what CDS returns through the API for your event. If CDS 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 CDS.

What should attendees enter on the login screen?

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