Beta Release Date: 10/30/2024
Release Date: TBD
Current Releases (as of 7/24/24) | ||||||
|---|---|---|---|---|---|---|
Cloud UI | Commerce | Identity (Auth0) | Identity (Legacy) | Unity | Arrival | Resort Tools |
Resort Tools 3.8 (Beta) |
|---|
Resolved Issues
Device-level Authentication Flow
We have implemented a device-level authentication flow for Resort Tools. Now, resort staff will be prompted to sign in to the application every month to provide an additional layer of protection for Resort Tools functionality. We’ve also implemented several security improvements to the admin experience.
A resort will be given two sets of credentials: admin and user. For configuring Resort Tools, the resort will sign in as an ‘admin,’ whereas to give the guests access to Resort Tools, the Resort will sign in using ‘user.' The authentication will be set by default to 30 days, and the Resort must sign in again on the terminal to give access to guests. Each terminal must be signed in separately.
Aspenware will give 1 admin and 1 user credential to the Resort. If those credentials are forgotten, compromised, or additional individuals need immediate credentials because the individuals who had them are out/away, a Freshdesk ticket must be submitted so Aspenware can generate additional credentials.