Who does this apply to?

Enterprise Customers familiar with page authentication using Oauth2 should entertain this setup.

Overview

Using Oauth2 for page authentication can allow you to verify a registrant's information before they can register for an event. As an added benefit you can use any information you may have about the registrant to prefill information about them on the page, as well lock down fields that you might not want them to edit, such as an internal ID, or perhaps information regarding previous qualifications. All of this data, when added to a field (hidden or visible) can be used in actions just like any user-entered data.

Requirements

Some development and a general understanding of Oauth2 flows will be required to implement this on your registration/ticketing page. You will be responsible for building out the endpoints for Oauth2 to connect to your desired authentication system/data.

Services like Auth0, Ping, and Okta can be used if you are looking for a hosted option. Any services that allow authentication using Oauth2 should be compatible with the page authentication described below.

Before you begin, ensure a solutions team member has enabled your account to use the Oauth2 Page Authentication feature.

Getting Started

To configure Oauth2 Page Authentication, select Restrict Access under the Settings dropdown in your page builder.

Enable Restrict Access and select OAuth2. Configure your Oauth2 Endpoints and mappings.

Data Endpoint Format

Your Data Endpoint can contain any JSON payload that fits your needs. The mapping will allow you to map the fields from your data endpoint to fields in the page. You will need to know the reference name of the field you want to map to inside of your page.

Finding A Fields Reference/ID

The reference name is listed under the Advanced Options of each field.

Mapping nested or complex fields

If you want to map data to a page fieldset that has multiple fields, such as address you can follow the pattern below.

{

"address": "address.street1",

"city": "address.city",

"state": "address.state",

"postal_code": "address.postalCode",

"country": "address.country"

}

The easiest way to find subkeys for a field is to use your browser’s inspector, inspect the field you want to reference and view the ng-model attribute for the field.

For example. To find out the street key for the address block we can right-click the field in the browser and select Inspect.

Then with the field highlighted in the inspector, we can see the last attribute for the ng-model string is street1.

Did this answer your question?