Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

  • Get the following information from Alterra (Steven Carrol <scarroll@alterramtnco.com>) for implementation:

    1. Client ID and Secret (unique per resort and for test vs. production)

      1. Prod Entitlements Client ID

      2. Test Entitlements Client ID

      3. Prod Entitlements Client Secret

      4. Test Entitlements Client Secret

      5. Test Redemption Client ID

      6. Prod Redemption Client ID

      7. Test Redemption Client Secret

      8. Prod Redemption Client Secret

    2. Resort Abbreviation (same in test and prod)

  • Send the following information to Alterra (Steven Carrol <scarroll@alterramtnco.com>) for testing and implementation:

    1. Resort name

    2. Test email addresses (that can receive emails)

    3. Resort callback urls (your pdp url, test and production)

...

Note

IMPORTANT: Enabling this feature does require an annual feature subscription fee. Talk to your Aspenware representative about adding this feature to your Aspenware Commerce subscription.

...

  • Go to Aspenware Commerce > Configuration > Local Plugins

    1. Locate “IKON Friends & Family” under the Aspenware Group and select Install.

  • Once installed Enable the plugin by selecting Edit next to the listed plugin and ensure the Is enabled checkbox is selected.

  • Now that the plugin is ready to be configured, ensure that you have the product set up that will be used for the Ikon Friends & Family component. To do this:

    1. Set up the product as you would normally. (See Configuring Products for basic product setup.)

    2. Note the product ID in the URL on the product configuration page. Consider that this may be different between your live and test environment if not performing copy live to tests frequently.

    3. Copy the product ID and add it to the Product ID field in Aspenware Commerce > Configuration > Local Plugins > IKON Friends & Family. Consider that this may be different between your live and test environment if not performing copy live to tests frequently.

  • Go back to the plugin (Aspenware Commerce > Configuration > Local Plugins > IKON Friends & Family) and select Configure.

    1. Under the General tab enter the two-letter abbreviation for your resort (if you do not know this abbreviation contact your Ikon pass representative).

    2. Under the General tab you will see the Logo Image url, leave as is

      1. Note that currently, this image is hard-coded.

    3. Select Save.

  • Go to the Language tab (second tab)..

    1. Enter the language you would like to appear in the bottom “toast” message when the responses noted above each text box are returned. See the example below.

    2. Select Save.

...

  • Go to the Ikon Login Configuration (third configuration tab).

    1. Enter the appropriate URL or endpoint as follows:

      1. Login Domain:

        1. IF test: https://account.uat.ikonpass.com

        2. IF production: https://account.ikonpass.com

      2. Login Endpoint: /login

      3. Redirect URI: [resort-pdp-url]/login-callback (see note below on how to configure)

        1. Note this will be different between test and prod and will need to be updated when copy live to tests occur.

    2. Select Save.

...

Note

IMPORTANT: For the redirect URI be sure to enter the URL from your resort’s PDP followed by “/login-callback”. This will return the logged-in Ikon Pass guest to the appropriate page.

  • https://[url to your friends and family tickets here]/login-callback

  • For example: https://myresort.friends-and-family-tix/login-callback

  • Go to the Ikon Entitlement API Configuration (fourth configuration tab). Most of the values will need to be obtained from your Ikon representative, while blackout dates will change according to year and pass type. See the image below for an example.

    1. Entitlements API domain:

      1. IF test: https://api.uat.ikonpass.com

      2. IF prod: https://api.ikonpass.com

    2. Entitlements Client ID: Value provided by Ikon Pass

      1. (Note that these values are different for test and production and from the redemption API.)

    3. Entitlements Client Secret: Value provided by Ikon Pass

      1. (Note that these values are different for test and production and from the redemption API.)

    4. Entitlements Token Endpoint: /token

    5. Entitlements Vouchers Endpoint: /v2/available-vouchers

      1. Note that this value may change as Alterra makes updates to their code. Aspenware will work closely with Alterra to stay informed of Endpoint changes.

    6. Ikon Pass Entitlement Type ID: This number is provided by Ikon Pass.

      1. For the 2021/2022 season, these values are in sync between test and production.

    7. Ikon Pass Blackout Dates: This number is provided by Ikon Pass.

    8. Ikon Base Plus Pass Entitlement Type ID: This number is provided by Ikon Pass.

    9. Ikon Base Plus Pass Blackout Dates: This number is provided by Ikon Pass.

    10. Ikon Base Pass Entitlement Type ID: This number is provided by Ikon Pass.

    11. Ikon Base Pass Blackout Dates: This number is provided by Ikon Pass.

    12. Ikon Local Pass Entitlement Type ID: This number is provided by Ikon Pass.Leave blank if you are not an IKON Local Resort.

    13. Ikon Local Pass Blackout Dates: Enter your local resort’s blackout dates. Leave blank if you are not an IKON Local Resort.

...

  • Redemption Api Domain:

    1. IF test: https://api-central-entitlements-uat.azurewebsites.net

    2. IF prod: https://api-central-entitlements.azurewebsites.net

  • Redemption Token Api Domain:

    1. IF test: https://api-identityserver4-uat.azurewebsites.net

    2. IF prod: https://api-identityserver4.azurewebsites.net

  • Redemption Client Id: Value provided by Ikon Pass and is unique per resort.

    1. Note that these values are different for test and production and from the redemption API.

  • Redemption Client Secret: provided by Ikon Pass (Unique per resort)

    1. Note that these values are different for test and production and from the redemption API.

  • Redemption Token Endpoint: /connect/token

  • Redemption Single Voucher Endpoint: /v1/redemptions/manual

    • Note that this value may change as Alterra makes updates to their code. Aspenware will work closely with Alterra to stay informed of Endpoint changes.

  • Redemption Grant Type: client_credentials

  • Redemption Scope: write_entitlements

  • Redemption Type Id: 6

...