You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Dispatcher can be configured using environment variables. These variables can be set directly in your shell or defined in a `.env` file for convenience.
3
+
Below are the key settings that can be adjusted to tailor the Dispatcher's behavior to your needs.
Each backend configuration can include the following fields:
39
+
40
+
-`client_credentials`: The client credentials for authenticating with the openEO backend. This is required if the `OPENEO_AUTH_METHOD` is set to `CLIENT_CREDENTIALS`. It is a single string in the format `oidc_provider/client_id/client_secret` that should be split into its components when used.
41
+
-`token_provider`: The provider refers to the OIDC IDP alias that needs to be used to exchange the incoming token to an external token. This is required if the `OPENEO_AUTH_METHOD` is set to `USER_CREDENTIALS`. For example, if you have a Keycloak setup with an IDP alias `openeo-idp`, you would set this field to `openeo-idp`. This means that when a user authenticates with their token, the Dispatcher will use the `openeo-idp` to exchange the user's token for a token that is valid for the openEO backend.
42
+
-`token_prefix`: An optional prefix to be added to the token when authenticating (e.g., "CDSE"). The prefix is required by some backends to identify the token type. This will be prepended to the exchanged token when authenticating with the openEO backend.
43
+
44
+
## Example Configuration
45
+
Here is an example of setting the environment variables in a `.env` file:
46
+
47
+
```env
48
+
# General Settings
49
+
APP_NAME="APEx Dispatch API"
50
+
APP_DESCRIPTION="APEx Dispatch Service API to run jobs and upscaling tasks"
0 commit comments