# Configuration

## Appmixer Engine

#### APP\_NAME

The authentication popup windows do contain the *Appmixer* title by default. If you want to change that, set the APP\_NAME env variable in the Appmixer engine.

![](https://4257661311-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FkpyTqJi517UiwFJJRydZ%2Fuploads%2Fgit-blob-54d2307486c62b39f9b4d3a7c406df2e99325ea8%2FACME_and_Appmixer.png?alt=media)

Example from the docker-compose.yml

```
  engine:
    ...
    environment:
      - APP_NAME=ACME
    ...
```

#### LOG\_LEVEL

By default set to `info`. Can be changed to `error`, `warn` or `debug`.

#### LOG\_COMPONENT\_DATA\_MESSAGE

When set to `false`, the component's input/output messages won't be logged into Elasticsearch.

{% hint style="info" %}
Important! Appmixer Insights and Designer log messages won't contain any items if logging data messages are turned off.
{% endhint %}

#### APPMIXER\_HTTPS\_PROXY and APPMIXER\_HTTP\_PROXY

Set up a proxy using these ENV variables. All HTTP(S) requests from Appmixer will be redirected to the proxy URL.

### Token encryption

Most of the connectors in Appmixer require user authentication. That can be represented as OAuth access tokens, API keys, or username/password combinations.

If you want (and you should) to enable token encryption, set the ENCRYPTION\_ENABLED environment variable to `true`. Then you have to set the ENCRYPTION\_SECRET environment variable. These variables cannot be set through the Backoffice.

```bash
# Turning the encryption on
ENCRYPTION_ENABLED=true
# Setting the encryption secret (generate your own!)
ENCRYPTION_SECRET=0EC0136A5187A09E21D03819A0EFFD259070CE23213B260A1444412EFD910503
```

```sh
# Generate the encryption secret
openssl enc -aes-256-gcm -k secret -P -md sha1
# copy the 'key' and put it to ENCRYPTION_SECRET
```

{% hint style="danger" %}
If you lose the encryption secret, you will not be able to recover the encrypted tokens.
{% endhint %}