Overview
Access project (or rs-access-project) microservice is used as a backend for frontend. This service is used
by the Web UI to retrieve its configuration and to aggregate some microservices information. It is
a multitenant microservice,
deployed for each user project. Regards has another microservice with a similar role, rs-access-instance, but
dedicated to the system instance administration UI.
rs-access-project responsibilities :
- Handle the configuration of user's UI (UI modules, UI plugins and service plugins, like application's theme or layout)
- Proxy for several microservices :
- rs-admin: CRUD operations concerning users of project
- rs-catalog: search products in catalog in order to add service plugins applicable on each result
- rs-storage: handle quotas in order to limit downloaded files in an order by user
- rs-access-instance&- rs-catalog: Replace toponyms with geometries in search
 
| Concept | Compatibility | Description | 
|---|---|---|
| Multitenant | Yes | Can handle multiple tenants/projects | 
| Vertical scalability | No | Uses Jobs system | 
| Horizontal scalability | No | Service can not be deployed with multiple instances | 
You can learn how the service works with the conception section.
How to use
- Browse all REST API available endpoints.
How to configure
To understand the configuration of a specific tenant (aka project) see Import/export configuration section.
How to access source code
- Microservice source code is available on Github
- access-servicesmodule source included in this microservice is available on Github
- backend-for-frontendmodule source included in this microservice is available on Github
- UI Configurationmodule source included in this microservice is available on Github