mirror of
https://github.com/opencloud-eu/opencloud.git
synced 2026-03-31 13:52:10 -04:00
120887abcc
By setting GRAPH_LDAP_GROUP_CREATE_BASE_DN a distinct subtree can be configured where new LDAP groups are created. That subtree needs to be subordinate to GRAPH_LDAP_GROUP_BASE_DN. All groups outside for GRAPH_LDAP_GROUP_CREATE_BASE_DN are considered read-only and only groups below that DN can be updated and deleted. This is introduced for a pretty specific usecase where most groups are managed in an external source (e.g. a read-only replica of an LDAP tree). But we still want to allow the local administrator to create groups in a writeable subtree attached to that replica.
Graph service
The graph service provides the Graph API which is a RESTful web API used to access Infinite Scale resources. It is inspired by the Microsoft Graph API and can be used by clients or other services or extensions.
Manual Filters
Using the API, you can manually filter like for users. See the Libre Graph API for examples in the developer documentation. Note that you can use and and or to refine results.
Sequence Diagram
The following image gives an overview of the scenario when a client requests to list available spaces the user has access to. To do so, the client is directed with his request automatically via the proxy service to the graph service.
Caching
The graph service can use a configured store via GRAPH_STORE_TYPE. Possible stores are:
memory: Basic in-memory store and the default.ocmem: Advanced in-memory store allowing max size.redis: Stores data in a configured redis cluster.redis-sentinel: Stores data in a configured redis sentinel cluster.etcd: Stores data in a configured etcd cluster.nats-js: Stores data using key-value-store feature of nats jetstreamnoop: Stores nothing. Useful for testing. Not recommended in productive enviroments.
- Note that in-memory stores are by nature not reboot persistent.
- Though usually not necessary, a database name and a database table can be configured for event stores if the event store supports this. Generally not applicapable for stores of type
in-memory. These settings are blank by default which means that the standard settings of the configured store applies. - The graph service can be scaled if not using
in-memorystores and the stores are configured identically over all instances. - When using
redis-sentinel, the Redis master to use is configured viaGRAPH_CACHE_STORE_NODESin the form of<sentinel-host>:<sentinel-port>/<redis-master>like10.10.0.200:26379/mymaster.