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
|`poolMax`|`DB_POOL_MAX`| 10 | available connections|
64
64
65
65
### Keycloak Variables
66
66
67
67
The following variables enable and enforce the use of OIDC Bearer Authentication for requests to COMS
68
68
69
-
| Config Var | Env Var | Default | Notes |
70
-
| --- | --- | --- | --- |
71
-
|`enabled`|`KC_ENABLED`|| Whether to run COMS in OIDC mode, required for user-based access controls and integration with OIDC users |
72
-
|`clientId`|`KC_CLIENTID`|| Keycloak service client ID for COMS |
73
-
|`clientSecret`|`KC_CLIENTSECRET`|| Keycloak service client secret |
74
-
|`identityKey`|`KC_IDENTITYKEY`|| Specify using alternative JWT claims for user identification instead of the standard jwt.sub. Multiple claim attributes may be specified via a comma-separated list. COMS will attempt to search for the custom claim ordered based on how it is specified in this variable before falling back to jwt.sub if none are found. |
75
-
|`publicKey`|`KC_PUBLICKEY`|| If specified, verify all incoming JWT signatures off of the provided public key |
76
-
|`realm`|`KC_REALM`|| Keycloak realm ID for COMS |
77
-
|`serverUrl`|`KC_SERVERURL`|| Keycloak server url for COMS authentication |
|`enabled`|`KC_ENABLED`|| Whether to run COMS in OIDC mode, required for user-based access controls and integration with OIDC users|
72
+
|`clientId`|`KC_CLIENTID`|| Keycloak service client ID for COMS|
73
+
|`clientSecret`|`KC_CLIENTSECRET`|| Keycloak service client secret for COMS |
74
+
|`identityKey`|`KC_IDENTITYKEY`|| Specify using alternative JWT claims for user identification instead of the standard jwt.sub. Multiple claim attributes may be specified via a comma-separated list. COMS will attempt to search for the custom claim ordered based on how it is specified in this variable before falling back to jwt.sub if none are found. |
75
+
|`publicKey`|`KC_PUBLICKEY`|| If specified, verify all incoming JWT signatures off of the provided public key|
76
+
|`realm`|`KC_REALM`|| Keycloak realm ID for COMS|
77
+
|`serverUrl`|`KC_SERVERURL`|| Keycloak server url for COMS authentication|
78
78
79
79
### Object Storage Variables
80
80
81
81
The following variables enable and enforce the use of OIDC Bearer Authentication for requests to COMS
82
82
83
-
| Config Var | Env Var | Default | Notes |
84
-
| --- | --- | --- | --- |
85
-
|`enabled`|`OBJECTSTORAGE_ENABLED`|| Whether to run COMS with a default bucket |
86
-
|`accessKeyId`|`OBJECTSTORAGE_ACCESSKEYID`|| The Access Key for your S3 compatible object storage account |
87
-
|`bucket`|`OBJECTSTORAGE_BUCKET`|| The object storage bucket name |
88
-
|`endpoint`|`OBJECTSTORAGE_ENDPOINT`|| Object store URL. eg: `https://nrs.objectstore.gov.bc.ca`|
89
-
|`key`|`OBJECTSTORAGE_KEY`|| The base path for storage location |
90
-
|`secretAccessKey`|`OBJECTSTORAGE_SECRETACCESSKEY`|| The Secret Access Key for your S3 compatible object storage account |
Before running the application, you must make sure that your database is up to date with the latest schema migration. Run the following first before starting up the COMS app as a maintenance task:
154
154
155
-
```sh
155
+
```sh
156
156
docker run -it --rm --entrypoint '/bin/sh' -c 'npm run migrate' \
0 commit comments