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. 

However, this is just the beginning. In 2024, we plan to make massive inroads at numerous other Auth0-supported features like Passwordless and Social Sign-in to reduce any friction at login or signup.

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) identity 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

Email & Password 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.

User Experience

Login, Sign Up, and Create Customer

Open

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

• Date of birth

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.

User Experience

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 RTPOne have the concept of merging customers. Whenever customers are merged in the point of sale (i.e. RTPOne), 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 RTPOne), 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.

Google Analytics

We will track the following Google Analytics events based on the page location and user action indicated.

Monitoring & Alerting

Aspenware has setup performance monitoring through Application Insights. Internal teams at Aspenware will be alerted if there are any performance degradations (e.g. 10 sign-in failures within 5 minutes). Aspenware will assess performance on a regular basis to determine trends and consult with Auth0 to determine continual improvements in the system to ensure the delivery of 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 (Powered by Auth0).

• During office hours

  • Service representative to notify resort after being notified via Slack.

• After office hours

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

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, but some information will be new.

Implementation

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):

• RFID Account Lookup

• Usernames

• Rewards

• Siriusware Integration

Guests will continue to see the Legacy Identity page when using Arrival or 3rd party applications. All credentials will be validated and stored in RTP until a future release.

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.

Key Terms

Have Questions?

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