With great pleasure, Aspenware presents Aspenware Identity 2.11. This release is compatible and must be deployed jointly with Aspenware Commerce version 2.21 and Aspenware Unity version 3.16.
| Table of Contents |
|---|
Updates, Features, and Upgrades
A single custom font is now supported for those who use CSS to import their custom fonts. Font customizations will apply to the Identity application, but the email font will be standardized as Helvetica for all customers. Review the configuration guide for limitations and details: https://hub.aspenware.net/main/Identity-Theming-and-Content-Customization.999030803.html.
Resolved Issues
Better error messaging for guests who do not have a birth date defined on their profile but try to log in through Aspenware Identity.
Resort-initiated configuration steps: Work with your Aspenware Representative to update the content displayed to a guest when they try to log in but required information is missing from their account, requiring them to call. The associated string is account.create.information missing.
If a resort uses Aspenware Identity for authentication and if click tracking was turned on in SendGrid, for some email clients (namely Outlook 365), the URL for password reset links exceeded the URL length parameters for that email client and would get truncated, returning invalid.
Resort-initiated configuration steps: If you previously disabled click tracking from SendGrid, and wish to enable this, enable this setting in SendGrid and test a password reset flow using Identity.
For resorts that use a combination of Aspenware Identity and the Loyalty feature in Commerce, when guests are asked to enroll in the Loyalty Program from Identity, the content next to the enrollment checkbox now supports some HTML. See documentation for additional details on supported HTML.
Resort-initiated configuration steps: Reach out to your Aspenware Representative with the desired content to be displayed next to the Loyalty opt-in checkbox within Identity after reviewing documentation.
...
Known Issues
If a guest account and a non-guest account exist for the same email, the system will allow the guest to choose which account to claim when going through the claim account process. Ideally, the nonguest account will be selected for the guest. (expected to be resolved in 2.23 - the next major release)
Guests who do not have a birth date defined on their profile are not able to log in through Identity.(Expected to be resolved in 2.23 - the next major release)
For resorts using Identity, if you create an account with an email that already has an authentication profile associated with it and gets an error that the email already exists, then change the email to an email that does not have an associated authentication profile, the error persists until you exit the create account page and re-enter. (expected to be resolved in 2.23 - the next major release)
Aspenware Identity doesn’t automatically redirect the guest back to the PDP they were on prior to selecting to sign in unless they explicitly use a redirect URL where sign-in is required. This is a feature enhancement to Identity. (expected to be added in 2.23 - the next major release)
...