| Table of Contents |
|---|
Setup Checklist
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
1.INFRASTRUCTURE TASKSInfrastructure Tasks | |||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Prerequisite | 2. COMMERCE TASKS
| |||||||||||||||||||||||||||||||||||||
2. Commerce Tasks | |||||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||||
3.IDENTITY TASKSIdentity Tasks | |||||||||||||||||||||||||||||||||||||||
|
| ||||||||||||||||||||||||||||||||||||||
|
|
...
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
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:
Example: I consent to the Terms of the Rewards Program.
Terms and Conditions 1 - Copy for Link and link for modality
Example: Click here to read terms. (embedded link: www.mytermsandconditions.com)
The Terms and Conditions copy is customizable. The Following can be customized by sending the desired copy to your Aspenware Representative.
Consent Text - i.e. "Enroll in Boyne Rewards."
Consent Link URL - i.e. "https://www.[yourresort].com/terms.html "
Consent Link Text - i.e. "Click here to read terms and conditions."
The following settings need to be configured as well, depending on you want the Terms and Conditions features to behave. Again, please let your Aspenware Representative know your preferences.
Is Consented Default (is the checkbox checked initially)
Show Checkbox
Show Consent Text
Show Consent Link
Check Required
...
Setting
...
Values
...
Description
...
NEED SETTING NAME for Terms and Conditions 1 check box appearing
...
...
This should only be enabled if Loyalty is configured for your store. This checkbox will only appear if a customer who is logging in does not already have a Boyne Rewards loyalty sign up. By clicking the box and accepting, the guest would enroll in the program. In subsequent logins, T&C 1 would not appear.
...
NEED SETTING NAME for Terms and Conditions 1 check box default as checked/unchecked
...
...
This loyalty sign up checkbox can be set to be enabled by default or disabled by default.
...
NEED SETTING NAME for Terms and Conditions 2 check box appearing
...
...
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.
Identity needs to be integrated into the same version of Unity utilized by Commerce and Arrival if applicable. The Unity server needs to be able to accept inbound traffic from Identity. Aspenware will work with you to ensure required traffic for Identity to work is allowed through securely.
Set Up SSL and DNS
Aspenware also recommends that your resort use a custom domain for the Identity app, such as http://login.yourresort.com. This will also require Secure Sockets Layer (SSL) setup and DNS entry. If you don’t have Aspenware Commerce, you’ll also want to set up a custom FQDN and SSL for Unity as well, Commerce customers will already have this configured. This process will be very similar to the process to configure SSL for Commerce detailed in this guide: https://hub.aspenware.net/main/How-to-generate-.pfx-file-for-new%2Frenewed-SSL-cert.1429471268.html. Work with your Aspenware representative to upload this and also to set up SSL renewal annual reminders.
(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.
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. If you license Aspenware’s Loyalty modual within Commerce and Unity, this T&C checkbox can be checked to opt guests into a Loyalty program, updating their status in RTP|One. If you do not use the Loyalty module in Aspenware commerce, T&C checkbox can be enabled but will NOT link to any flag in RTP or in Identity. In order to complete this configuration, please collect the following below and work with your Aspenware representative to implement.
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:
Example: I consent to the Terms of the Rewards Program.
Terms and Conditions 1 - Copy for Link and link for modality
Example: Click here to read terms. (embedded link: http://www.mytermsandconditions.com )
The Terms and Conditions copy is customizable. The Following can be customized by sending the desired copy to your Aspenware Representative.
Consent Text - i.e. "Enroll in Boyne Rewards."
Consent Link URL - i.e. "https://www.[yourresort].com/terms.html "
Consent Link Text - i.e. "Click here to read terms and conditions."
The following settings need to be configured as well, depending on you want the Terms and Conditions features to behave. Again, please let your Aspenware Representative know your preferences.
Is Consented Default (is the checkbox checked initially)
Show Checkbox
Show Consent Text
Show Consent Link
Check Required
Setting | Values | Description |
|---|---|---|
NEED SETTING NAME for Terms and Conditions 2 check box default as checked/unchecked |
| This Terms and Conditions sign up checkbox can be set to be enabled by default or disabled by default. |
HINT: The following HTML elements are supported in checkbox labels:
<b> <strong> <i> <em> <a> <span> <p>
href and the target attributes on an <a> tag. This means that <a href=”google.com” target=”_blank”>Google</a> will render as a working link.
Additionally, <b>, <strong>, <i>, and <em> can be used to format labels with bold or italics if desired. <p> and <span> can be used to break up the content or force line breaks.
Any tags or attributes not listed above will not render. They will be stripped out of the HTML before the content is rendered to the page. This is to ensure that nobody is inserting <script> tags or other elements that could lead to security risks or broken layouts.
| Info |
|---|
NOTE: Terms and Conditions (T&Cs) will be present on the account creation page, login page, and account capture page in an identical fashion. Only the first (Terms and Conditions-1) will execute an action - enroll the customer in the rewards program. Each additional Terms and Conditions are also customizable but do not trigger any action. Any additional Terms & Conditions would require Agreement Copy as well as Copy for link and link for modality. |
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
...
1 check box appearing |
| This should only be enabled if Loyalty is configured for your store. This checkbox will only appear if a customer who is logging in does not already have a Boyne Rewards loyalty sign up. By clicking the box and accepting, the guest would enroll in the program. In subsequent logins, T&C 1 would not appear. |
NEED SETTING NAME for Terms and Conditions 1 check box default as checked/unchecked |
| This loyalty sign up checkbox can be set to be enabled by default or disabled by default. |
NEED SETTING NAME for Terms and Conditions 2 check box appearing |
| Can be used for generic terms and condition agreement. If enabled, this checkbox would appear on every login, and would not record the action taken by the guest. |
NEED SETTING NAME for Terms and Conditions 2 check box default as checked/unchecked |
| This Terms and Conditions sign up checkbox can be set to be enabled by default or disabled by default. |
HINT: The following HTML elements are supported in checkbox labels:
<b> <strong> <i> <em> <a> <span> <p>
href and the target attributes on an <a> tag. This means that <a href=”google.com” target=”_blank”>Google</a> will render as a working link.
Additionally, <b>, <strong>, <i>, and <em> can be used to format labels with bold or italics if desired. <p> and <span> can be used to break up the content or force line breaks.
Any tags or attributes not listed above will not render. They will be stripped out of the HTML before the content is rendered to the page. This is to ensure that nobody is inserting <script> tags or other elements that could lead to security risks or broken layouts.
| Info |
|---|
NOTE: Terms and Conditions (T&Cs) will be present on the account creation page, login page, and account capture page in an identical fashion. Only the first (Terms and Conditions-1) will execute an action - enroll the customer in the rewards program. Each additional Terms and Conditions are also customizable but do not trigger any action. Any additional Terms & Conditions would require Agreement Copy as well as Copy for link and link for modality. |
...
Commerce Tasks
1. Install and Enable the Identity Plugin in Aspenware Commerce
...
Find and install the Identity Plugin
In the Aspenware Commerce admin panel go to Configuration > Local Plugins
Search the list for ExternalAuth Methods : Identity Authentication
Select Install.
Once installation is complete, select Restart application to apply changes at the top of the page.
| Info |
|---|
NOTE: This restart can take up to 7 minutes to complete and should occur during low-traffic times. |
Configure Identity External Authentication
Go to Configuration > External Authentication
If the Identity plugin has been successfully installed you will see it on the admin screen.
Select Configure.
Enter your OpenID, ClientID, and OpenID ClientSecret (these are created and provided by Aspenware).
In the Authority to use when connecting to OpenID field enter the web address (URL) that will be using Identity.
Select Save.
Return to the External Authentication Admin page and select Edit.
Select the check box under the Is active column then select Update.
Identity Tasks
Settings
The following settings are configurable in Identity and must be set at the Identity client level (configurable per external applications). These cannot be controlled through an Admin interface and must be done by the Aspenware Dev Ops team, contact your Aspenware representative to update these settings.
...
Setting | Values | Description |
|---|---|---|
RequireAccountVerification | True/False | If an account is found, if TRUE, guest will be texted or emailed a code to verify that they are allowed to claim the account, if FALSE, the guest will be able to create an authentication profile on a found account with no verification required. |
CheckPassMediaForFindUser | True/False | If TRUE, guest can login using their pass media or RFID number. If FALSE, login with pass number is disabled. If set to true, there are language strings that should be setup to reflect that this is allowed for guests as well. |
AgeLimit | 13 is the default | Age limit for guests to create accounts |
PasswordExpiredEnabled | True/False | When set to TRUE this setting will enforce a password reset for all users logging in through identity with an RTP password date change of today (automatically set in Azure) minus the “PasswordChangeDays” set below. If FALSE, guests will never be forced to reset their password. |
PasswordChangeDays | 750 is the default | Only needed if PasswordExpiredEnabled is True. This setting subtracts the number of days from today’s date to determine how recently users must have changed their password in order not to force a reset. For example, if set to 7, any user who has created their account or reset their password in the past week will not be sent down the password reset flow. |
NEED SETTING NAME for Terms and Conditions 1 check box appearing |
| This should only be enabled if Loyalty is configured for your store. This checkbox will only appear if a customer who is logging in does not already have a Boyne Rewards loyalty sign up. By clicking the box and accepting, the guest would enroll in the program. In subsequent logins, T&C 1 would not appear. |
NEED SETTING NAME for Terms and Conditions 1 check box default as checked/unchecked |
| This loyalty sign up checkbox can be set to be enabled by default or disabled by default. |
NEED SETTING NAME for Terms and Conditions 2 check box appearing |
| Can be used for generic terms and condition agreement. If enabled, this checkbox would appear on every login, and would not record the action taken by the guest. |
NEED SETTING NAME for Terms and Conditions 2 check box default as checked/unchecked |
| This Terms and Conditions sign up checkbox can be set to be enabled by default or disabled by default. |
...