Gateway Service Configuration
Introduction
The Infinite Scale Gateway service is responsible for passing requests to the storage providers. Other services never talk to storage providers directly but will always send their requests via this service.
Caching
The gateway service can use a configured store via the global OCIS_CACHE_STORE
environment variable.
Note that for each global environment variable, a service-based one might be available additionally. For precedences see Environment Variable Notes. Check the configuration section below. Supported stores are:
Store Type | Description |
---|---|
|
Basic in-memory store and the default. |
|
Stores data in a configured Redis Sentinel cluster. |
|
Stores data using key-value-store feature of NATS JetStream. |
|
Stores nothing. Useful for testing. Not recommended in production environments. |
|
(deprecated) Advanced in-memory store allowing max size. |
|
(deprecated) Stores data in a configured Redis cluster. |
|
(deprecated) Stores data in a configured etcd cluster. |
|
(deprecated) Stores data using the key-value-store feature of NATS JetStream. |
Other store types may work but are currently not supported.
The gateway service can only be scaled if not using the memory store and the stores are configured identically over all instances!
|
If you have used one of the deprecated stores of a former version, you should reconfigure to use one of the supported ones as the deprecated stores will be removed in a later version. |
- Store specific notes
-
-
When using
redis-sentinel
:
The Redis master to use is configured via e.g.OCIS_CACHE_STORE_NODES
in the form of<sentinel-host>:<sentinel-port>/<redis-master>
like10.10.0.200:26379/mymaster
. -
When using
nats-js-kv
:-
It is recommended to set
OCIS_CACHE_STORE_NODES
to the same value asOCIS_EVENTS_ENDPOINT
. That way the cache uses the same nats instance as the event bus. -
Authentication can be added, if configured, via
OCIS_CACHE_AUTH_USERNAME
andOCIS_CACHE_AUTH_PASSWORD
. -
It is possible to set
OCIS_CACHE_DISABLE_PERSISTENCE
to instruct nats to not persist cache data on disc.
-
-
Configuration
Environment Variables
The gateway
service is configured via the following environment variables. Read the Environment Variable Types documentation for important details.
Name | Type | Default Value | Description |
---|---|---|---|
|
bool |
false |
Activates tracing. |
|
string |
|
The type of tracing. Defaults to '', which is the same as 'jaeger'. Allowed tracing types are 'jaeger' and '' as of now. |
|
string |
|
The endpoint of the tracing agent. |
|
string |
|
The HTTP endpoint for sending spans directly to a collector, i.e. http://jaeger-collector:14268/api/traces. Only used if the tracing endpoint is unset. |
|
string |
|
The log level. Valid values are: 'panic', 'fatal', 'error', 'warn', 'info', 'debug', 'trace'. |
|
bool |
false |
Activates pretty log output. |
|
bool |
false |
Activates colorized log output. |
|
string |
|
The path to the log file. Activates logging to this file if set. |
|
string |
127.0.0.1:9143 |
Bind address of the debug server, where metrics, health, config and debug endpoints will be exposed. |
|
string |
|
Token to secure the metrics endpoint. |
|
bool |
false |
Enables pprof, which can be used for profiling. |
|
bool |
false |
Enables zpages, which can be used for collecting and viewing in-memory traces. |
|
string |
127.0.0.1:9142 |
The bind address of the GRPC service. |
|
string |
tcp |
The transport protocol of the GRPC service. |
|
string |
|
The secret to mint and validate jwt tokens. |
|
string |
com.owncloud.api.gateway |
The CS3 gateway endpoint. |
|
string |
|
TLS mode for grpc connection to the go-micro based grpc services. Possible values are 'off', 'insecure' and 'on'. 'off': disables transport security for the clients. 'insecure' allows using transport security, but disables certificate verification (to be used with the autogenerated self-signed certificates). 'on' enables transport security, including server certificate verification. |
|
string |
|
Path/File name for the root CA certificate (in PEM format) used to validate TLS server certificates of the go-micro based grpc services. |
|
bool |
false |
Disables the loading of user’s group memberships from the reva access token. |
|
bool |
true |
Commit shares to storage grants. This grants access to shared resources for the share receiver directly on the storage. |
|
string |
Shares |
Name of the share folder in users' home space. |
|
bool |
true |
Disable creation of the home space on login. |
|
string |
|
The storage transfer secret. |
|
int |
86400 |
Expiry for the gateway tokens. |
|
string |
noop |
The type of the cache store. Supported values are: 'memory', 'redis-sentinel', 'nats-js-kv', 'noop'. See the text description for details. |
|
[]string |
[127.0.0.1:9233] |
A list of nodes to access the configured store. This has no effect when 'memory' or 'ocmem' stores are configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details. |
|
string |
cache-providers |
The database name the configured store should use. |
|
Duration |
5m0s |
Default time to live for user info in the cache. Only applied when access tokens has no expiration. See the Environment Variable Types description for more details. |
|
int |
0 |
The maximum quantity of items in the cache. Only applies when store type 'ocmem' is configured. Defaults to 512 which is derived from the ocmem package though not explicitly set as default. |
|
bool |
false |
Disables persistence of the provider cache. Only applies when store type 'nats-js-kv' is configured. Defaults to false. |
|
string |
|
The username to use for authentication. Only applies when store type 'nats-js-kv' is configured. |
|
string |
|
The password to use for authentication. Only applies when store type 'nats-js-kv' is configured. |
|
string |
memory |
The type of the cache store. Supported values are: 'memory', 'redis-sentinel', 'nats-js-kv', 'noop'. See the text description for details. |
|
[]string |
[127.0.0.1:9233] |
A list of nodes to access the configured store. This has no effect when 'memory' or 'ocmem' stores are configured. Note that the behaviour how nodes are used is dependent on the library of the configured store. See the Environment Variable Types description for more details. |
|
string |
cache-createhome |
The database name the configured store should use. |
|
Duration |
5m0s |
Default time to live for user info in the cache. Only applied when access tokens has no expiration. See the Environment Variable Types description for more details. |
|
int |
0 |
The maximum quantity of items in the cache. Only applies when store type 'ocmem' is configured. Defaults to 512 which is derived from the ocmem package though not explicitly set as default. |
|
bool |
false |
Disables persistence of the create home cache. Only applies when store type 'nats-js-kv' is configured. Defaults to false. |
|
string |
|
The username to use for authentication. Only applies when store type 'nats-js-kv' is configured. |
|
string |
|
The password to use for authentication. Only applies when store type 'nats-js-kv' is configured. |
|
string |
https://localhost:9200 |
The public facing URL of the oCIS frontend. |
|
string |
spaces |
The driver name of the storage registry to use. |
|
[]string |
[] |
The rules for the storage registry. See the Environment Variable Types description for more details. |
|
string |
|
Additional configuration for the storage registry in json format. |
|
string |
|
Mount ID of this storage. Admins can set the ID for the storage in this config option manually which is then used to reference the storage. Any reasonable long string is possible, preferably this would be an UUIDv4 format. |
YAML Example
-
Note the file shown below must be renamed and placed in the correct folder according to the Configuration File Naming conventions to be effective.
-
See the Notes for Environment Variables if you want to use environment variables in the yaml file.
# Autogenerated
# Filename: gateway-config-example.yaml
tracing:
enabled: false
type: ""
endpoint: ""
collector: ""
log:
level: ""
pretty: false
color: false
file: ""
debug:
addr: 127.0.0.1:9143
token: ""
pprof: false
zpages: false
grpc:
addr: 127.0.0.1:9142
tls: null
protocol: tcp
token_manager:
jwt_secret: ""
reva:
address: com.owncloud.api.gateway
tls:
mode: ""
cacert: ""
skip_user_groups_in_token: false
commit_share_to_storage_grant: true
share_folder_name: Shares
disable_home_creation_on_login: true
transfer_secret: ""
transfer_expires: 86400
cache:
provider_cache_store: noop
provider_cache_nodes:
- 127.0.0.1:9233
provider_cache_database: cache-providers
provider_cache_ttl: 5m0s
provider_cache_size: 0
provider_cache_disable_persistence: false
provider_cache_auth_username: ""
provider_cache_auth_password: ""
create_home_cache_store: memory
create_home_cache_nodes:
- 127.0.0.1:9233
create_home_cache_database: cache-createhome
create_home_cache_ttl: 5m0s
create_home_cache_size: 0
create_home_cache_disable_persistence: false
create_home_cache_auth_username: ""
create_home_cache_auth_password: ""
frontend_public_url: https://localhost:9200
storage_registry:
driver: spaces
rules: []
json: ""
storage_users_mount_id: ""