integration config instructions moved to its own readme, readme secti…

…ons rearranged

README.md

@@ -8,14 +8,12 @@ A subscription / access to Akamai Edge Workers is required to utilize this conne
 >You can find the latest released version and deployable bundle "kuedge.tar.gz" [here](https://github.com/queueit/KnownUser.V3.Akamai/releases/latest).
 
 ## Installation
-### Note: EdgeWorker should be created using the Dynamic Compute resource tier.
+
+_Note: EdgeWorker should be created using the Dynamic Compute resource tier._
 Installing the edge worker the first time requires uploading an archive file (TGZ format) to the Edge Worker manager in the Akamai Control Center. Once uploaded, the service worker code can be customized and updated with specific configurations (protection schema) managed and exported from the Queue-it GO Platform. 
  - Step 1: Download all js files plus bundle.json and create bundle and upload to Akamai Edge Worker manager **
  - Step 2: Create desired waiting room(s), triggers, and actions in GO. Then, save/publish the Configuration. 
- - Step 3: Provide integration config by implementing one of the following methods.
-   - 3.1 Manually updating integration config within Edge worker code
-   - 3.2 Dynamically download and cache integration config
-   - 3.3 Push integration config to Akamai EdgeKV   
+ - Step 3: Provide integration config [READ MORE](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/IntegrationConfig.md)
  - Step 4: Upload the Queue-it edge worker bundle
  - Step 5: Update the bundle.js file in the Edge Worker manager with a new version and deploy the new version of EdgeWorker
  - Step 6: In Akamai Propery, add queue-it required **hidden** variables named as 
@@ -30,110 +28,17 @@ Installing the edge worker the first time requires uploading an archive file (TG
 
 ** https://learn.akamai.com/en-us/webhelp/edgeworkers/edgeworkers-user-guide/GUID-53F43F70-BEBC-4BA4-A2FB-3F23A6125106.html 
 
-### Providing the queue configuration
-The configuration specifies a set of Triggers and Actions. A Trigger is an expression matching one, more or all URLs on your website. 
-When a user enter your website and the URL matches a Trigger-expression the corresponding Action will be triggered. 
-The Action specifies which queue the users should be send to. 
-In this way you can specify which queue(s) should protect which page(s) on the fly without changing the server-side integration.
-
-This configuration can then be used in Edge Worker by three ways.
-
-### 3.1 Manually updating integration config within Edge worker code
-Latest integration config can be downloaded from GO Queue-it Platform and then updated by replacing "inlineIntegrationConfig" variable value in integrationConfigProvider.js file.
-To use the inline integration config, set 'QUEUEIT_CONFIG_TYPE' queue-it variable value to 'inline' in Akamai property manager.
-
-### 3.2 Dynamically download and cache integration config
-#### NOTE: If you are deploying to a staging environment that has an IP-filter applied, make sure to whitelist the path to the integration config, so the IP-filter doesn’t apply. Otherwise, the Queue-it Edge Worker will be blocked from accessing the configuration path. 
-Integration config can be downloaded by calling Queue-IT API endpoint and then cached in Akamai network. In Akamai property manager, set variables 'PMUSER_QUEUEIT_CONFIG_TYPE' to 'cache' and 'PMUSER_QUEUEIT_API_KEY' to your API key. Configure the following Akamai property rules by setting the criteria, out going request path and caching behavior to download and cache the integration config.
-
-#### Edgeworker rule
-Define edgeworker rule in Akamai property and set criteria as illustrated in picture.
-
-![Edge worker criteria](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/edgeworkerCriteria.png)
-
-#### Download integration config rule
-Define property rule to download integration config and add following configuration illustrated in the pictures.
-
-![Download integration config criteria](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/integrationConfigDownloadCriteria.png)
-
-![Download integration config Behaviour](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/integrationConfigDonloadBehavior.png)
-
-![Download integration config Outgoing Path](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/outgoingRequestPath.png)
-
-![Download integration config cache](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/integrationConfigCache.png)
-
-![Download integration config cache prefresh](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/cachePrefreshing.png)
-
-### 3.3 Push integration config to Akamai EdgeKV
-Before you start using Akamai edgekv to store and fetch integration config, make sure that you have entitlements for both EdgeKV products on contract.
-Integration config can be pushed and stored in Akamai EdgeKV from GO Queue-it Platform. Connector can fetch stored integration config from Edgekv by setting the 'PMUSER_QUEUEIT_CONFIG_TYPE' variable to 'edgekv' in Akamai property manager. Apply the following steps to setup and use integration config from EdgeKV in the connector.
-
-- Get access to Akamai EdgeKV and its API. Read details about EdgeKV in Akamai documentation.
-- Download Akamai client credentials and these credential will be used to complete the following step in GO Queue-it Platform.
-- Update and publish integration config in GO Queue-it Platform.
-- Generate Akamai EdgeKV token from GO Queue-it Platform and copy into 'lib/edgekv_tokens.js' file in the connector code.
-- Push integration config to Akamai EdgeKV from GO Queue-it Platform. 
-
-#### Assign roles and permissions
-You need to assign roles to create and manage access to EdgeKV in Akamai Control Center.
-Administrator can add individual users, then create and assign roles and access rights. You can find detailed instructions for managing users, roles, and permissions in the Akamai Identity and Access Management online help.
-
-#### Set up authentication for an API client:
-- Create an API client with the necessary credential for a single Control Center account. This credential applies to all APIs for all products you currently have access to with that Control Center account.
-- Launch Identity and Access Management. In Control Center, you can navigate there by selecting → ACCOUNT ADMIN → Identity & access.
-- From the Users and API Clients tab, click New API client for me to open the Customize API client screen.
-- Click Quick to instantly create an API client with the necessary credential. This client’s API access levels, group roles, and permissions are identical to your current login.
-- You can verify the APIs you can access by clicking Show additional details. Enter the API service’s name in the Filter field to verify that it’s included and that you have the proper level of access.
-
-![Akamai API Client](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/apiClient.png)
-
-#### Generate API client credentials
-To make EdgeKV API calls over the Akamai network, you first need to generate API credentials. 
-
-- To use EdgeKV management APIs or the Edge KV CLI, the API credentials need to be created using the Admin role.
-- To add permissions to your API credentials go to the Account Admin > Identity & access section in Akamai Control Center.
-- On the Users and API Clients tab, use the search bar to find your Client Name and open the client details.
-- Click the Edit API client button and scroll down to the APIs section.
-- Click the Select APIs radio button and type edgekv in the search bar.
-- Select the EdgeKV API.
-- Select READ-WRITE from the Access Level dropdown and submit your changes.
-- Download the credentials from API client page in Akamai control center
-
-![Access Level Edgekv API](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/accessLevelEdgekvAPI.png)
-
-#### Akamai Settings in Go Queue-IT Platform
-EdgeKV API host url is required to store integration config and generate the EdgeKV token for edgeworker. Add host url in 'Web End Point' field on Integration => Overview => Settings page. 
-You can find Akamai host url from API client page in Akamai control center.
-
-![Akamai Host Settings](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/hostSettings.png)
-
-#### Generate EdgeKV token
-Queue-IT connector needs Akamai EdgeKV API token to get integration config from EdgeKV. The token can also be generated using Akamai EdgeKV CLI/API. GO Queue-it Platform also has functionality to generate and retrieve EdgeKV tokens on a button click which reduce the complexity of using Akamai API/Cli. Currently, it is only possible to generate one token to use in both environments (staging/production). Default life time of the token is 6 months if generated from GO Queue-it Platform. Generate or retrieve the Akamai EdgeKV tokens by providing the required information in GO Queue-it Platform (on integration overview page).
-
-##### Important Note: Remember to generate new token before existing one expires and update the 'lib/edgekv_tokens.js' file.
-
-![Retrieve token](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/pushConfigForm.png)
-![Generate token](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/generateToken.png)
+## Adding a Site Failover behaviour
+EdgeWorks may fail to execute, the first time they are run on an EdgeServer, so it is recommended to add a Site Failover behaviour to perform a retry when the EdgeWorker execution fails.
 
-#### Push integration config
-Integration config can be pushed to Akamai EdgeKV from GO Queue-it Platform by providing Akamai client credentials and environment. This process will initialize the EdgeKV if it is not initialized and then create namespace "QueueIT", group "integrations" and item "integrationConfig" in EdgeKV to store integration config. Following picture shows the required information to push the integration config.
+First, create a PMUSER variable, with an arbitrary name, and set the value to %(AK_HOST):
 
-![Akamai Push Config Form](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/pushConfigForm.png)
+![Site Failover PMUSER Variable](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/failover1.png)
 
-#### Update token in edgeworker bundle
-Copy the valid token name and value from GO Queue-it Platform and update 'lib/edgekv_tokens.js' file in Edgeworker code bundle to get integration config from EdgeKV.
-Edgekv library will use this token to authenticate the request from edgeworker.
-```
-var edgekv_access_tokens = {
-  "namespace-QueueIT" : { 
-    "name": "Name of the token",
-    "value" : "Value of the token"
-    }
-}
-export { edgekv_access_tokens };
-```
+Then add a Site Failover behaviour that uses the PMUSER variable from above, and has the following settings:
+![Site Failover Behaviour](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/failover2.png)
 
-### QueueIT variables
+## QueueIT variables
 To integrate with QueueIT Akamai connector it is required to define queueit variables in your Akamai property.   
 These variables should be named as 'PMUSER_QUEUEIT_CUSTOMERID', 'PMUSER_QUEUEIT_CONFIG_TYPE', 'PMUSER_QUEUEIT_SECRET_KEY', 'PMUSER_QUEUEIT_API_KEY' 
 and of type **Hidden** in Akamai property manager. The following table describes the options for variable values.
@@ -146,19 +51,11 @@ and of type **Hidden** in Akamai property manager. The following table describes
 | PMUSER_QUEUEIT_API_KEY | If 'PMUSER_QUEUEIT_CONFIG_TYPE' is set to cache  | Find your Api key in the GO Queue-it Platform. |
 | PMUSER_QUEUEIT_EXECUTED | For validation that the Queue-It EdgeWorker was executed | The Queue-It EdgeWorker will set the variable to `true`. This variable can be used in Akamai Property Manager to apply alternative logic if the EdgeWorker was not executed. | 
 
-### Adding a Site Failover behaviour
-EdgeWorks may fail to execute, the first time they are run on an EdgeServer, so it is recommended to add a Site Failover behaviour to perform a retry when the EdgeWorker execution fails.
-
-First, create a PMUSER variable, with an arbitrary name, and set the value to %(AK_HOST):
-
-![Site Failover PMUSER Variable](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/failover1.png)
-
-Then add a Site Failover behaviour that uses the PMUSER variable from above, and has the following settings:
-![Site Failover Behaviour](https://github.com/queueit/KnownUser.V3.Akamai/blob/master/documentation/failover2.png)
+## Advanced features
 
 ### Using EnQueueToken
 A token could be used for queueing the users. This makes it even more protected. The token will be included when the user is redirected from Akamai to the queue and vice versa. [QueueToken](https://github.com/queueit/QueueToken.V1.JavaScript) package has been used to generate this token. The generated token will be valid for 1 minute.
 
 To use the EnqueueToken follow the below steps:
 - The waiting room should be configured to accept this token. This configuration could be made in Queue-it Go platform.
-- SHOULD_INCLUDE_ENQUEUETOKEN variable should be set to ```true``` in the ```main.js``` file.
+- SHOULD_INCLUDE_ENQUEUETOKEN variable should be set to ```true``` in the ```main.js``` file.