Aspenware presents Unity 3.41 and Identity (Auth0) 1.3
Note: Beta release notes are drafts of what will be included in the upcoming release. They are subject to change and may be altered due to findings during beta testing.
Beta Release Date: 9/12/2023Release Date: 9/18/19/2023
...
Current Releases (as of 9/18/23) | ||||||
|---|---|---|---|---|---|---|
Cloud UI | Commerce | Identity (Auth0) | Identity (Legacy) | Unity | Arrival | Resort Tools |
1.3 | 3. |
41 |
...
Commerce 2.44.4 Release Notes |
|---|
Resolved Issues
For Cloud customers, a small backend change was made to remove unused code related to ResortOS cookies that was causing conflicts when creating production releases.
Resorts that use Heartland as their payment gateway were experiencing an error if a guest tried to update their stored credit card under the My Account/Resort Charge tab. The bug has been fixed, and the feature is working as expected.
Unity 3.41 Release Notes |
|---|
Enhancements
Full-length state names are now converted to the appropriate abbreviation when stored in RTP.
Unity now imposes expiration dates on loyalty rewards, gift cards, etc. The expiration date can be calculated based on enrollment, event, or amenity date or a defined “Change of Terms” date.
...
Identity (Auth0) 1.3 Release Notes |
|---|
Identity (Auth0) is the next generation of Aspenware Identity with a migration to a best-in-class identity provider, Auth0. This platform will bring security, maintenance, and user experience benefits such as passwordless and social login options.
Introducing Identity (Auth0) 1.3
We have enhanced our new Identity solution, powered by Auth0, in this release. The feature currently supports Alterra’s integration with their own Auth0-powered login flow. This foundation will pave the way for future releases and for other Aspenware Cloud resorts who wish to onboard Identity (Auth0). This release is focused on optimizing performance, streamlining multiple Auth0 actions into a single call, and extending guest data synchronization to include Billing Address and Primary Phone Number.
| Note |
|---|
IMPORTANT: Identity (Auth0) 1.3 must be deployed with Commerce version 2.44.3 and Unity version 3.41 at a minimum. |
Enhancements
Billing Address and Billing Phone number from Alterra’s Guest API now sync from their guest database to the POS.
Previously, when signing in via Alterra Auth0, multiple calls were made. Now only one call is made to reduce the load time.
Users are now redirected to an error page if any error occurs between Identity (Auth0) and Commerce. The user will be prompted to try to sign in again.
...