Aspenware Commerce, Aspenware Arrival and resort mobile apps can optionally use Identity for authentication and Single Sign On (SSO). This feature decreases duplicate customer accounts in the POS, logs customers into all platforms utilizing Identity seamlessly, and provides more security for password updating.
This feature is supported for: Resorts using RTP|One as a POS. Separate Identity license required.
This feature is not supported for: Resorts using Siiriusware as a POS.
Feature Description
Aspenware Commerce, Aspenware Arrival, and resort mobile apps can optionally use Identity for authentication- enabling a customer to be signed in across all platforms that use Identity. When Identity is setup and configured, turning on Identity for Aspenware Commerce is enabled through installing a plugin and several settings within the Commerce platform. Benefits to using Identity for Commerce Authentication rather than native Commerce authentication include:
Implicit find-me flows are more likely to catch guests who already have accounts, routing them to find their accounts and decreasing duplicate customers in your POS.
If multiple applications use Identity as an authentication platform, a guest who is logged in to Aspenware Arrival will also be logged in to Aspenware Commerce and the mobile app, so they can seamlessly navigate between applications.
More security than standard login as Identity can require guests to reset their password if the password change date in RTP|One is past today’s date.
For more information on Identity, please see Identity documentation.
Like this page? Click the like button below. Don't like this page and/or want to give feedback about this page, leave a comment below and Aspenware will address to improve this article.