Platform

In this section, we learn how to configure OpenCTI to have it tailored to our production and development needs.

Here are the configuration keys, for both Docker (environment variables) and manual deployment.

The equivalent of a config variable in environment variables is the usage of a double underscores (__) for a level of config. Example: "providers": { "ldap": { "strategy": "LdapStrategy" } } will become PROVIDERS__LDAP__STRATEGY=LdapStrategy

If you need to put a list of element for the key, it must have a special formatting. Example for redirect uris for openid config:

"PROVIDERS__OPENID__CONFIG__REDIRECT_URIS=[\\"<https://demo.opencti.io/auth/oic/callback\\"]">

To change the allowed memory of the platform process, you can use the environment variable NODE_OPTIONS=--max-old-space-size=8096 (where 8096 is the amount of memory in MB).

API / Front

Example to enforce references:

"enforce_references": [
      "Threat-Actor",
      "Intrusion-Set",
			...
]

Schedulers / engines

Dependencies

Worker

The Python worker can be configured manually using the configuration file config.yml or through environment variables.

Python worker

Dependencies

Dependencies have their own set of configuration that you can found in their specific documentation.

Sometime the documentation doesn't have every options so we try to fill the gap here.