Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

With great pleasure, Aspenware presents 

  • Unity 3.41

  • 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/14/2023

Release Date: 9/18/2023


Current Releases

(as of 9/18/23)

Cloud UI

Commerce

Identity (Auth0)

Identity (Legacy)

Unity

Arrival

Resort Tools

1.1

3.0

1.3

2.32

3.41

1.9

3.7


Unity 3.41 Release Notes

New Features

Enhancements

Resolved Issues

Full-length state names are now converted to the appropriate abbreviation when storing in RTP.


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: Tailored for Alterra Resorts

Specifically tailored for Alterra Resorts, Identity (Auth0) 1.3 has exciting enhancements. This release is laser-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.

While exclusive to Alterra Resorts, these features pave the way for forthcoming releases to other resorts that wish to onboard with Identity (Auth0).

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.

  • No labels