Overview:
In order to access the Cost Per Use endpoint, there are 2 header elements which will need to be passed with each request
(1)Authorization token
(2)Encrypted customer id

This story is about the Encrypted customer id

When making requests to Cost Per Use endpoint for a customer, an encrypted customer id needs to be passed in as part of request header.

Define where mod-kb-ebsco-java will store encrypted id associated with a customer
This is similar to what we are storing in kb_credentials file for HoldingsIQ access - although only encrypted customer id is passed into request

Also plan to have both a prod and sandbox endpoint for access:
https://apis.ebsco.com/uc
https://apis.ebsco.com/uc-sandbox

See
for added details on APIGEE and encrypted customer id