Overview: Identity v3 (Powered by Auth0)

Key Terms

Identity v3 (Powered by Auth0)

Aspenware Identity v3 (Powered by Auth0) marks a significant leap forward in secure, reliable, and modern identity features for our valued customers. In addition to the basic login & sign-up features, this product includes customer matching logic that will help reduce duplicate customers and account for any merging of customers in RTP.

As part of Aspenware’s ongoing commitment to safety and efficiency when rolling out new products and features, we will closely monitor and evaluate data in Auth0 and in Google Analytics. This ensures smooth operations and a seamless experience for all stakeholders. 

What is Auth0?

Auth0 is an identity access management (IAM) provider. An IAM solution is a gatekeeper to the resources you provide to customers as web applications, APIs, etc, adding layers of authentication to secure your users’ digital identities and your product. The Auth0 identity platform supports regular web, mobile, or machine-to-machine apps.

The Identity v3 (Powered by Auth0) platform allows Aspenware to customize login services to fit your business, technology, and customer base.

Why Auth0?

• Best in-class identity access management platform

• Secure platform

• Ability to easily extend into SSO, social, biometrics, MFA, and passwordless which has been proven to increase conversion rates

• Quick onboarding experience for customers.

Product Features

Sign in & Create Account

Your guests can utilize a standard login & create account flow using an email and password. The guest will be required to remember these credentials every season unless they decide to switch to other methods such as passwordless, which will be available in an upcoming release.

For any existing customer in RTP that signs in and has any missing information that is required upon sign up, the guest will be prompted with ‘complete your profile’ and be asked to input any missing data. For example, if a customer/user exists in RTP with all fields except phone number, the guest will be shown only phone number field and be required to complete prior to signing in.

Note. If a new guest signs up and doesn’t complete their profile here, RTP will be populated with a first and last name of the guests email address. Due to RTP requirements and how auth0 works in conjunction, we must populate those fields so we can associated the auth0 account with an RTP customer ID. Once the user completes the process of signing up, those fields will be replaced by their values they enter for first and last name.

Open

Create User Account

Customer Matching

Guests that sign in create a user account. The user account is mapped to a customer in the point of sale (POS). It's vital to limit duplicate customer creation in the POS when possible. For that reason, Aspenware created a customer matching feature. When a guest creates a new user account, they will be prompted to complete their profile, which creates a customer record in the POS. When the provided information matches an existing customer in the POS, we send them through a matching process in order to prevent creation of a duplicate customer. Aspenware will endeavor to prevent a duplicate and will attempt to match with the following information (must match to all):

• Email (In RTP, this is an email profile)

• First

• Last

If the customer matched to only one (1) customer in the POS, Aspenware will send an email to the customer for them to verify that they are the owner of that email. Once verified, the customer will then be matched. The new Auth0 user account will be associated to the customer record found in the POS, and they can then sign in and purchase products on the resort commerce site.

If the customer matched to multiple customers in point of sale, the guest is presented with the resort’s phone number so they can call for help. At this point, Aspenware systems don’t know which customer to match to and will leave it up to the call center to make the determination with the customer.

The resort maintains responsibility over what to do when a guest matches to multiple customers. In order to address this issue, when the resort receives the call from the customer, one option is to merge those customers in the POS and then direct the guest to enter the credentials they previously created when attempting to create an account the first time. From there, the guest will receive the ‘account already exists’ message and be required to verify their email before logging in successfully.

Email Verification

Anytime verification is required (e.g. account linking or customer matching), the customer will receive an email with a code so they can verify as a second ‘factor.' The email will look something similar to the example below.

SMTP

Email verifications will be sent from Auth0 using an SMTP provider.

Supported SMTP Providers: Sendgrid (Recommended), Mailgun, Mandrill, Amazon SES, Microsoft 365, Sparkpost, and Azure.

It is strongly recommended that the resort utilize an SMTP provider and have a dedicated IP address for transactional emails. This will significantly increase the likelihood of guests receiving emails for any verification needs.

Merged Customers

Some point of sales, like RTP|One have the concept of merging customers. Whenever customers are merged in the point of sale (i.e. RTP|One), Aspenware’s platform will associate the user to the merged customer record. If two customers are merged in the point of sale that have different user accounts in Auth0 (i.e. a different authentication profile in RTP|One), the user is associated with the customer record containing their credentials.

Guest Checkout

Guest checkout is supported out of the box with Identity v3 (Powered by Auth0). When a customer is purchasing a product that doesn’t require authentication, they will be presented with the option to log in if the email has been recognized as a previous account. If selected, they will be routed to the Identity v3 (Powered by Auth0) login screen to authenticate.

Pass Media Account Lookup (Forgot Email)

Some guests may have forgotten which email they used to sign up. If this feature is enabled, resorts can allow guests to look up their email by inputting their pass number. Aspenware will configure Auth0 to enable this function so that once the user selects ‘Lookup email by pass number,' they will be directed to another page to input their pass number, as shown below.

Creating an Account with a Pass

While account creation with a pass is supported in Identity v2, Identity v3 (Powered by Auth0) offers a more intuitive and streamlined experience. One of the key benefits of signing up with a pass is that guests can easily link new purchases to their existing pass.

How it Works:

1. Enter Pass Number: Guests begin by entering their pass number. Aspenware will check if an account already exists for the guest.

2. Email Profile Verification: If no existing account is found, Aspenware will then verify if there is an email associated with the guest's profile in RTP|One.

3. Email Invitation: If an email is found, Aspenware will send a verification email inviting the guest to confirm their identity.

4. Account Creation: The guest verifies their account by accepting the email invite, setting up a password, and completing their customer profile information. Once these steps are completed, the sign-up process is done!

If the guest already has an account, they will be redirected to sign-in if it’s been determined that an email exists in the auth profile in RTP|One for that pass.

If a guest enters a valid pass number, but the pass is not associated with an email, Aspenware will prevent the guest from signing up with that pass. This safeguard ensures that individuals who may have found or obtained someone else's pass cannot create an account with it.

In these cases, guests will be prompted to contact the resort for assistance in verifying and linking their pass to their account.

Bot Detection

Auth0 provides built-in bot detection and protection against unauthorized login attempts that can be enabled for partner resorts. When suspicious activity is detected, such as from certain IP addresses, Auth0 will prompt the user with a simple challenge, such as checking a box to confirm they are human.

Single Sign-On

Single Sign-On

Single Sign-On, or SSO is enabled with Aspenware. In the instance of a Resort Group with multiple resorts, a single guest can create credentials at one resort and use those same credentials across all related resorts, as long as the tenant is setup to do so.

Multi-Store SSO

Identity v3 will allow resort groups that utilize a shared Commerce instance to host multiple stores. This applies to various configurations:

• Themes are applied per store

• GTM IDs are applied per store

• Logins are applied per store

Rewards

The Rewards module in RTP|One is integrated with Aspenware Identity v3 (Powered by Auth0). If a resort chooses to enable a rewards program, an enrollment checkbox will appear during the customer profile creation process. When selected, this will communicate directly with RTP|One and set the guest's enrollment status to "true" in the Rewards module.

Please note that the resort must configure their Rewards module in RTP|One before Aspenware can activate this feature in the sign-up flow.

Google Analytics

We have added Google Analytics tracking to Identity v3. For more information on the specific additions to the data layer, see Identify v3 (Powered by Auth0) Configuration Guide.

Monitoring & Alerting

Aspenware has implemented performance monitoring using Application Insights. Internal teams at Aspenware will receive alerts if any performance issues arise, such as multiple sign-in failures (e.g., 10 failures within 5 minutes). Aspenware regularly evaluates system performance to identify trends and works closely with Auth0 to continuously improve the platform, ensuring optimal performance for resort partners.

How will we alert the resort?

Aspenware will notify the resort if there are any significant performance issues affecting Identity v3.

• During office hours

  • Customer Success Representative to notify resort after being notified via Slack.

• After office hours

  • On-call Representative will notify resort after being notified via Slack.

3rd Party Applications

All existing (and new) 3rd party applications from Identity v2 are may be added to Identity v3. See the Identify v3 (Powered by Auth0) Configuration Guide for details about setup of this feature.

Aspenware will provide documentation and consultation if/when resorts wish to migrate their applications to using Identity v3 (Powered by Auth0). Please contact your Aspenware Service Agent for more information.

Theming

Aspenware will theme the resort Auth0 pages based on the criteria submitted via Theme Designer. If the resort is a current Aspenware customer, most of the information can be utilized from Identity v2, but some new information will be required.

Theming the Auth0 pages will be part of the resort implementation process. All requests will go through the Aspenware Team and they will be responsible for setting up the initial theme on the resort Identity v3 pages once the tenant is setup.

Other Considerations

Currently, the following functions are not supported with Identity v3 (Powered by Auth0):

• Usernames

• Siriusware Integration

Have Questions?

Check out our Frequently Asked Questions page or contact your Aspenware Service Agent.