...
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 the used to sign-up with originally. If enabled, Resorts can allow a guest to look up their email by inputting their pass number, as seen below. To enable this function, Aspenware will set the setting: "passMediaLookupEnabled": true, "customerIdLookupEnabled": true.
...
Once the user selects ‘Lookup email by pass number,' they will be directed to another page to input their pass number, seen below.
...
Create Account with Pass
Though supported in v2, creating an account with a pass in v3 is much more intuitive and obvious. The benefit of signing up with a pass is that the guest will be able to potentially link new purchases to their existing pass.
First, the guest will input their pass number and Aspenware will first check to determine if an account exists already for the guest, and then a second check will occur if the guest has an email profile so we can verify their ownership of the pass itself.
If no existing account exists and there is an email profile on their customer profile in RTP, Aspenware will send an email to verify the guests identity by sending an email ‘invite.' The guest will verify their account by accepting the invite and add a password to their account. From there, they only have to add their customer profile information and they’re done signing up.
...
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 for that pass.
...
If the guest enters a valid pass number but the customer associated with the pass doesn’t have an email, they cannot verify they own the pass and hence, Aspenware will prevent them from signing up with that pass. This is to prevent individuals who may have picked up this pass off the ground or through other means to create an account with someone else's pass. These individuals will be asked to call the resort for assistance.
...
Bot Detection
Bot detection and preventing brute force attacks is out-of-the-box functionality that Aspenware will enable for partner resorts. For any suspicious IP Addresses, auth0 will present a ‘challenge' to the user to check a box that they are indeed 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 use the same credentials created at one Resort at another, 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 is connected to Aspenware Identity v3. If a resort wants to enable a rewards program and enroll guests, an enrollment checkbox will appear on the create customer profile screen. This will then communicate directly with RTP and create an enrollment status of ‘true’ in the module. Please note that the resort must setup their own Rewards module in RTP before Aspenware would enable this feature on the sign-up flow.
Google Analytics
We will track the following Google Analytics google analytics events based on the page location and user action indicated.
Title | Description | Location | Type (Page/Event) |
|---|---|---|---|
Sign-in Page | When a customer views sign in page | Auth0 | Page View |
Forgot password page | Customer view ‘forgot password’ page | Auth0 | Page View |
forgot_password_select | Customer selected ‘forgot password’ | Auth0 | Event |
forgot_password_submitted | Customer sent email to themselves to reset password | Auth0 | Event |
signin_attempt | Customer selects ‘continue’ from sign in | Auth0 | Event |
signin_error | Customer experiences a sign in error, such as password didn’t match, account exists, etc. |
Event
authentication_success
Auth0 | Event | ||
successful_login | Customer has been authenticated and directed to shop successfully | AW Cloud UI & Commerce | Event |
signup_selection | Customer selects ‘sign up’ in auth0 | Auth0 | Event |
Sign-up Page | Customer views sign up page | Auth0 | Page View |
signup_attempt | Customer selects ‘continue’ after input email/password when creating a new account | Auth0 | Event |
signup_success | Customer is successful in creating new account in auth0 | Auth0 | Event |
auth0_account_error | Error occurred during sign up in auth0 such as email in use, API error. | Auth0 | Event |
Customer profile page | Customer views create customer profile page | AW Cloud UI | Page View |
customer_match | Customer submits create profile and is matched to an existing customer in RTP (1 or many) | AW Cloud UI | Event |
Customer match (1) page | Customer views ‘verification needed’ page after match | AW Cloud UI | Page View |
Customer match (many) page | Customer view ‘call resort’ after being matched to multiple customers in RTP | AW Cloud UI | Page View |
create_profile | Customer is successful in creating new customer | AW Cloud UI | Event |
Update_Customer_Profile_Error | Customer experienced an error at creating a new customer | AW Cloud UI | Event |
account_lookup | Customer selects ‘look up account with pass’ | Auth0 | Event |
account_found | Customer inputs a valid pass and found an account | Auth0 | Event |
account_notfound | Customer input an invalid pass or no account found | Auth0 | Event |
signupwithpass_invitesent | Customer inputs correct pass, has email on file, and has no auth profile | Auth0 | Event |
Property: error_accountexists | Customer inputs a valid pass but account exists | Auth0 | Event |
Property: error_incorrectnumber | Customer inputs a invalid pass number and nothing found. | Auth0 | Event |
error_noemail | Customer inputs a valid pass but no email profile exists to verify | Auth0 | Event |
Add password | When a guest lands on the add password screen |
| Page View |
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.
...
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.
3rd Party Applications
All existing (and new) 3rd party applications from Identity v2 are applicable to be added to Identity v3. There are additional requirements and collaboration required between the Resort and Aspenware to setup, as listed below:
Steps for Onboarding 3rd Party Applications
Resort completes the application section on the onboarding form and sends to Aspenware.
Application Description
Application type
Callback URL
Logout URL
withScheme
Aspenware sets up auth0 applications for the Resort 3rd party application.
Aspenware will provide resort with connection name and scope to put in their application(s) code-base.
Resort Dev team to setup application using auth0 guidelines: https://auth0.com/docs/quickstart/native
Resort Dev team to test.
The documentation for setup can be found /wiki/spaces/PLA/pages/3188031491.
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.
...