...
| Tip |
|---|
This feature is supported for Aspenware Cloud customers who have contracted with Auth0. |
| Warning |
|---|
This feature is not supported for resorts using Siriusware. |
Key Terms
| Excerpt |
|---|
ActionsSecure, tenant-specific, versioned functions written in Node.js that execute at certain points during the Auth0 runtime. Actions are used to customize and extend Auth0's capabilities with custom logic. ApplicationsSoftware that relies on Auth0 for authentication and identity management. Auth0 supports single-page, regular web, native, and machine-to-machine applications. BiometricsAuthentication process that allows the user to leverage FaceID or Fingerprint scanning. ConnectionRelationship between Auth0 and the sources of users for your applications. Examples include identity providers (such as Google or Active Directory), passwordless authentication methods, or user databases. Custom DomainThird-party domain with a specialized, or vanity, name. Also known as a CNAME. OrganizationsAuth0 product that allows B2B customers to categorize end-users and define specific roles, login experience, and access to resources. TenantsA logically-isolated group of users who share common access with specific privileges to a single software instance. |
Identity v3 (Powered by Auth0)
...
The Identity v3 (Powered by Auth0) identity platform allows Aspenware to customize login services to fit your business, technology, and customer base. Using the Auth0 Dashboard and Management API, we can create a custom Auth0 instance to authenticate and authorize your customers. We can configure login behaviors, connect your user data store, manage those users, choose an authorization grant, and establish authentication factors for a seamless, scalable product with an impactful user experience.
Why Auth0?
Best in-class identity access management platform
Most secure platform
Out-of-the-box features and functionality that support Secure platform
Ability to easily extend into SSO, social, biometrics, MFA, passwordless, etc.
Quick onboarding experience for customers.
Proven increase of conversion rates via universal login.
...
Anytime verification is required (e.g. account linking , or customer matching, etc.), 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.
...
Guest checkout is supported out of the box with auth0Identity 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 auth0 Identity v3 (Powered by Auth0) login screen to authenticate.
...
We will track the following 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 pageAuth0 | Page View | |
Forgot password page | Customer view ‘forgot password’ pageAuth0 | 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. | Auth0 | Event |
authentication_success | Customer has successfully been authenticated by auth0 | Auth0 | Event |
successful_login | Customer has been authenticated and directed to shop successfullyAW Cloud UI | 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 pageAW 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 matchAW 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 |
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.
What are we measuring?
...
Auth0 Uptime
...
...
Error trends
Performance Standards for Login & Create Account
0.1 - 5 seconds: Expectation
5.1 - 10 seconds: Warnings
10.1+ seconds: Alerts
How will we alert the resort?
...
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 Auth0 resort Identity v3 pages once the tenant is setup.
Updates
Any updates to the theme must be submitted to the Aspenware Service Team via the Service Portal. The Aspenware Service Agent will make any supported adjustments to the theme via Theme Designer.
Other Considerations
Currently, the following functions are not supported with Identity v3 (Powered by Auth0)”
RFID Account Lookup
Guest checkout
Rewards
Siriusware Integration
We offer partial support for Aspenware Arrival and other 3rd party applications as follows:
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
| Excerpt |
|---|
ActionsSecure, tenant-specific, versioned functions written in Node.js that execute at certain points during the Auth0 runtime. Actions are used to customize and extend Auth0's capabilities with custom logic. ApplicationsSoftware that relies on Auth0 for authentication and identity management. Auth0 supports single-page, regular web, native, and machine-to-machine applications. BiometricsAuthentication process that allows the user to leverage FaceID or Fingerprint scanning. ConnectionRelationship between Auth0 and the sources of users for your applications. Examples include identity providers (such as Google or Active Directory), passwordless authentication methods, or user databases. Custom DomainThird-party domain with a specialized, or vanity, name. Also known as a CNAME. OrganizationsAuth0 product that allows B2B customers to categorize end-users and define specific roles, login experience, and access to resources. TenantsA logically-isolated group of users who share common access with specific privileges to a single software instance. |
Have Questions?
Check out our Frequently Asked Questions page or contact your Aspenware Service Agent.