File-based Configuration¤

Introduction¤

This page documents how to configure cmemc via configuration files.

cmemc looks for a default configuration file on a reasonable place depending on your operating system:

For Linux, this is $HOME/.config/cmemc/config.ini.
For Windows, this is %APPDATA%\cmemc\config.ini.

If you need to change this location and want use another config file, you have the following options:

you can always run cmemc with the --config-file path/to/your/config.ini option, or
you can set a new config file with the environment variable CMEMC_CONFIG_FILE, or
you can set the XDG_CONFIG_HOME variable to something different than $HOME/.config/ (this will also change the config location of all other XDG Base Directory Specification aware tools).

However, once you start cmemc the first time and without any command or option, it will create an empty config file at this location and will output a general introduction.

First cmemc run …

$ cmemc
Empty config created: /home/user/.config/cmemc/config.ini
Usage: cmemc [OPTIONS] COMMAND [ARGS]...

  eccenca Corporate Memory Control (cmemc).

  cmemc is the eccenca Corporate Memory Command Line Interface (CLI).

  Available commands are grouped by affecting resource type (such as graph,
  project and query). Each command and group has a separate --help screen
  for detailed documentation. In order to see possible commands in a group,
  simply execute the group command without further parameter (e.g. cmemc
  project).

  If your terminal supports colors, these coloring rules are applied: Groups
  are colored in white; Commands which change data are colored in red; all
  other commands as well as options are colored in green.

  Please also have a look at the cmemc online documentation:

                      https://eccenca.com/go/cmemc

  cmemc is © 2022 eccenca GmbH, licensed under the Apache License 2.0.

Options:
  -c, --connection TEXT  Use a specific connection from the config file.
  --config-file FILE     Use this config file instead of the default one.
                         [default: /Users/seebi/Library/Application
                         Support/cmemc/config.ini]

  -q, --quiet            Suppress any non-error info messages.
  -d, --debug            Output debug messages and stack traces after errors.
  --version              Show the version and exit.
  -h, --help             Show this message and exit.

Commands:
  admin       Import bootstrap data, backup/restore workspace or get status.
  config      List and edit configs as well as get config values.
  dataset     List, create, delete, inspect, up-/download or open datasets.
  graph       List, import, export, delete, count, tree or open graphs.
  project     List, import, export, create, delete or open projects.
  query       List, execute, get status or open SPARQL queries.
  vocabulary  List, (un-)install, import or open vocabs / manage cache.
  workflow    List, execute, status or open (io) workflows.

You can now edit your config file and add credentials and URL parameter for your Corporate Memory deployment. You either search the config manually in your home directory or you can use the config edit command, which opens the config file in your default text editor (specified with the EDITOR variable).

$ cmemc config edit
Open editor for config file /home/user/.config/cmemc/config.ini

The rules for the config file are similar to a Windows INI file and are explained in detail at docs.python.org.

Examples¤

Example

[my-local]
CMEM_BASE_URI=http://localhost/
OAUTH_GRANT_TYPE=client_credentials
OAUTH_CLIENT_ID=cmem-service-account
OAUTH_CLIENT_SECRET=...

Here is a minimal example using the client_credentials grant type.

This creates a named section my-local which is a connection to a Corporate Memory deployment on http://localhost/. The authorization will be done with a system account cmem-service-account and the given client secret. Using this combination of config parameter is based on a typical installation where, all components are available under the same hostname.

Example

[my-local]
CMEM_BASE_URI=http://localhost/
OAUTH_GRANT_TYPE=password
OAUTH_CLIENT_ID=cmemc
OAUTH_USERNAME=user
OAUTH_PASSWORD=...

Another example using password grant type.

This creates a named section my-local which is a connection to a Corporate Memory deployment on http://localhost/. The authorization will be done with the given OAUTH_USERNAME and the OAUTH_PASSWORD.

Configuration Variables¤

The above example provides access to an installation where all components including keycloak are deployed with the default URL base. However, if you need to fine tune all locations or want to use special functionality, the following config file parameters can be used to do this.

The following configuration variables specify where cmemc can find the relevant HTTP endpoints. Most of them are optional.

CMEM_BASE_URI¤

This is the base location (HTTP(S) URL) of your eccenca Corporate Memory deployment.

You always have to set this configuration variable.

This variable defaults to http://docker.localhost/.

DI_API_ENDPOINT¤

This is the base location (HTTP(S) URL) of all Data Integration APIs.

Usually you do not need to set this configuration variable.

This variable defaults to $CMEM_BASE_URI/dataintegration/.

DP_API_ENDPOINT¤

This is the base location (HTTP(S) URL) of all Data Platform APIs.

Usually you do not need to set this configuration variable.

This variable defaults to $CMEM_BASE_URI/dataplatform/.

OAUTH_TOKEN_URI¤

This is OpenID Connect (OIDC) OAuth 2.0 token endpoint location (HTTP(S) URL).

Usually you do not need to set this configuration variable.

This variable defaults to $CMEM_BASE_URI/auth/realms/cmem/protocol/openid-connect/token.

The following configuration variables specify how cmemc can fetch a token in order to authenticate with this token on the endpoints.

OAUTH_GRANT_TYPE¤

This configures the used OAuth Grant Type in order to specify how cmemc is able to get a valid token for accessing the Corporate Memory APIs.

Depending on the value of this variable, other authentication related variables will become mandatory or obsolete. The following values can be used:

client_credentials - this refers to the OAuth 2.0 Client Credentials Grant Type. Mandatory variables for this grant type are OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET or OAUTH_CLIENT_SECRET_PROCESS.
password - this refers to the OAuth 2.0 Password Grant Type. Mandatory variables for this grant type are OAUTH_CLIENT_ID, OAUTH_USER, OAUTH_PASSWORD or OAUTH_PASSWORD_PROCESS.
prefetched_token - this value can be used in case you can provide a token which was fetched outside of cmemc. Mandatory variables for this grant type are OAUTH_ACCESS_TOKEN or OAUTH_ACCESS_TOKEN_PROCESS.

OAUTH_CLIENT_ID¤

This configures the used client ID. Ususally, the following cmemc related clients are configured in the standard Corporate Memory realm:

cmem-service-account is the client which is configured to be used with the client_credentials grant type.
cmemc is the client which is configured to be used with the password grant type.

You usually have to set this configuration variable (exception: you use the prefetched_token grant type).

This variable defaults to cmem-service-account.

OAUTH_USER¤

This variable specifies your user account.

You only need to set this configuration variable in case you use the password grant type.

This variable defaults to admin.

OAUTH_PASSWORD¤

This variable specifies your user password.

You only need to set this configuration variable in case you use the password grant type.

OAUTH_CLIENT_SECRET¤

This variable specifies your client secret (password).

You only need to set this configuration variable in case you use the client_credentials grant type.

OAUTH_ACCESS_TOKEN¤

This variable specifies a prefetched access token.

You only need to set this configuration variable in case you use the prefetched_token grant type.

OAUTH_PASSWORD_PROCESS¤

In order to avoid saving credentials in config files you can use this optional configuration variable instead of the OAUTH_PASSWORD variable.

Please refer to Getting Credentials from external Processes for more information.

This variable defaults to none.

OAUTH_CLIENT_SECRET_PROCESS¤

In order to avoid saving credentials in config files you can use this optional configuration variable instead of the OAUTH_CLIENT_SECRET variable.

Please refer to Getting Credentials from external Processes for more information.

This variable defaults to none.

OAUTH_ACCESS_TOKEN_PROCESS¤

In order to avoid saving credentials in config files you can use this optional configuration variable instead of the OAUTH_ACCESS_TOKEN variable.

Please refer to Getting Credentials from external Processes for more information.

This variable defaults to none.

SSL_VERIFY¤

Setting this to True will disable certification verification (not recommended).

Please refer to Certificate handling and SSL verification for more information.

This variable defaults to False.

REQUESTS_CA_BUNDLE¤

Setting this to a PEM file allow for using private Certificate Authorities for certificate validation.

Please refer to Certificate handling and SSL verification for more information.

This variable defaults to $PYTHON_HOME/site-packages/certifi/cacert.pem.

File-based Configuration¤

Introduction¤

Examples¤

Configuration Variables¤

Location related¤

CMEM_BASE_URI¤

DI_API_ENDPOINT¤

DP_API_ENDPOINT¤

OAUTH_TOKEN_URI¤

Authentication related¤

OAUTH_GRANT_TYPE¤

OAUTH_CLIENT_ID¤

OAUTH_USER¤

OAUTH_PASSWORD¤

OAUTH_CLIENT_SECRET¤

OAUTH_ACCESS_TOKEN¤

OAUTH_PASSWORD_PROCESS¤

OAUTH_CLIENT_SECRET_PROCESS¤

OAUTH_ACCESS_TOKEN_PROCESS¤

Network related¤

SSL_VERIFY¤

REQUESTS_CA_BUNDLE¤