Configuration: Identity

Setup Checklist

This section is a comprehensive and high level summary of all tasks and prerequisites required for this feature to function properly. This section is purposed for use after an administrator is familiar with configuring this feature as an “audit” checklist. For detailed set-up instructions, jump down to “Prerequisite Tasks” and “Detailed Setup Guide” and then follow up with this checklist to ensure all steps are completed.

Prerequisite Tasks

This section describes all requirements that must be completed before you can begin setting up this feature. Once these tasks are complete continue to the next section.

Infrastructure Tasks

• Terms and Conditions

Identity can be configured to allow guests to review and execute Terms and Conditions as a part of the account creation or sign-in process. In order to complete this configuration, please collect the following below and then send an email to service@aspenware.com. In the email, request that your Identity server be configured for use with Loyalty. Include all required copy and links, organized by T&C 1, T&C 2, etc. Be sure to include your preference for the default setting (checked or unchecked for each T&C setting.)

• Terms & Conditions 1 (T&C 1)- Agreement Copy:

  1. Example: I consent to the Terms of the Rewards Program.

  2. Terms and Conditions 1 - Copy for Link and link for modality

     1. Example: Click here to read terms. (embedded link: www.myrewards.com)

• Set Up Azure Architecture

  Identity requires Azure setup to create the web application and database and encryption keys in the Azure Key Vault. The Identity App Service can exist with the App Service Plan that also hosts Commerce and Arrival App Services. The Identity database stores configuration for the Aspenware Identity application. This database can consistently be set to an s3 service level under normal and increased traffic times. One database is used for both production and test.

  

• Set Up SSL and DNS

Aspenware also recommends that your resort use a custom domain such as login.yourresort.com. This will also require Secure Sockets Layer (SSL) setup and DNS entry.

• (Optional) Set Up Twilio for Integration

Although not required, if your resort desires a custom number for Twilio communications, Aspenware is happy to integrate with individual Twilio accounts. For setup, we will need Twilio Account SID, Account API Token, and the From Number. Contact your Aspenware representative for assistance with this.

Settings, Language Strings and/or HTML Widgets for this Application

This feature may require updates to the following settings, language strings and/or HTML Widgets. Learn more about how to update and create Settings, Language Strings, and HTML widgets follow the links to the respective section.

Settings

• Email Template Customization

Both Identity password emails and verification code emails have standard email templates for forgot password emails and account verification emails. Email templates can be customized to include the resorts logo, links to the resort website, resort address in the email footer, and the resort name.

Language Strings

Updating Messaging in Identity

Most language strings within Identity are configurable. These language strings are updated using a JSON file and will be defined during the implementation process of Identity. Most language strings can retain default values, however the following language strings are recommended for customization. View a full list of language strings.

• Login Page Configurable Language Strings

• Reset Password Page

• Create Account Page

• Claim Account

• Force Password Reset (Only if setting PasswordExpirationEnabled is true)

Detailed Setup Guide

Theming for Identity

When using Identity, your client folder will include a background image and your logo image. Horizontal logo images are recommended when using the Identity application. In addition to language strings (listed above), below are the components that resorts may configure upon implementing Identity. All other UI features default to the application.

1. Background

   1. Background Image

   2. Background Overlay (for text readability)

2. Logo (long and wide logos work best)

   1. Logo URL

   2. Logo Sizes for Mobile, Tablet and Desktop

3. Primary Color (Buttons, Mobile Header Bar)

4. Button Details

   1. Button Color

   2. Button Radius (rounding)

   3. Button Hover Color

   4. Button Font Weight (Bold, Normal, etc)

   5. Button Font Size

   6. Button Letter Spacing

5. Font Details

   1. Heading Font Color

   2. Body Font Color

   3. Link Font Color

   4. Link Hover Font Color

   5. A single custom font can be 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. Supply the font URL to your Aspenware Representative, similar to the example below:
      

      

Multiple store-fronts and Identity

Aspenware Commerce can be configured to have multiple store-fronts operating from a single backend admin instance, where product configuration for the shop is done. Each storefront can have its own look and feel, language strings, custom domain, settings, products, and more. Similarly, Identity can be configured to work with multiple storefronts. A single instance of Identity can also be configured to work with multiple completely separate Aspenware Commerce stores, so that if you are logged in to one store you are logged into others, however, there are some limitations around what can be customized across store-fronts or unique shops for Identity.

If using the same Identity across multiple storefronts and/or stores, the custom URL across the single instance of Identity must remain constant. For example, Boyne Resorts uses a single Identity across all of its 7 resorts, so http://shop.bigskyresort.com redirects to http://id.boyneresorts.com but guests coming to this page from the Big Sky shop or Arrival see a Big Sky branded experience and language strings that correspond to Big Sky.

Other limitations include language strings, if two stores are operating out of a single Aspenware Commerce Instance, i.e. they share an admin backend, then they can have unique branding, but the language strings must remain the same across the stores. If two stores use the same Identity but have separate Aspenware Commerce admin instances, they can have unique brands AND language strings. For example, Boyne Mountain and Boyne Highlands, sister resorts in Michigan also use the same Identity as the other Boyne Resorts (http://id.boyneresorts.com ), however, these two storefronts share a single Aspenware Commerce Admin, so the Identity language strings for these two store-fronts are shared. In the image below, the items in yellow are shared across the store front’s views of identity, and the items in blue are unique.

Checklist

Use this checklist when customizing the Identity theme to ensure all steps are completed.