Administration

Public and private keys

Generate the key files and store them to config/site/[identifier]/wise/. The following linux command could be used to generate the key files:

openssl genrsa -out private.pem 2048
openssl rsa -pubout -in private.pem -out public.pem

Site configuration

  1. Define an url segment challenge for wise events in the site configuration for the property wise.eventUrlSegmentChallenge. For security reasons prefer something cryptic like wdoufkyrkLoqaarxxvmdxyyj.
  2. Define where to store event and credit transaction records by setting the property wise.storageUid in the site configuration. The property can contain a single uid or a coma separated list of uid’s. In the later case the first uid will be used to store new records.
  3. Create a read only API token in your wise account (see below) and assign its key to the property wise.apiTokenKey.
  4. Optionally define the directory where the typo3 command is located in the property wise.binDirectory
Example wise properties in site configuration
wise:
  eventUrlSegmentChallenge: wdoufkyrkLoqaarxxvmdxyyj
  storageUid: 1
  apiTokenKey: '11111111-1111-1111-1111-111111111111'
  binDirectory: ../vendor/bin

Wise account

  1. Register the event handler with a webhook. The webhook properties are:

    • Subscription event: Balance deposits
    • URL: [https://domain.ch]/wise-event-handler-[url segment challenge]

    Hint

    Replace [url segment challenge] with the value previously assigned to the site configuration property wise.eventUrlSegmentChallenge.

  2. Create an API token with “read only” permissions and assign its key to the site configuration property wise.apiTokenKey.

  3. Add the public key from config/site/[identifier]/wise/public.pem to the API tokens.