Access Control
Description
The access control module is responsible for user and access management. It is designed to ensure role-based access control (RBAC).
Access Control within DATAMITE architecture
Access Control workflow
Prerequisites
- Docker
- Docker Compose
Installation
-
Clone the repository:
git clone https://gitlab.eclipse.org/eclipse-research-labs/datamite-project/data-security/access-control.git
-
Navigate to the access-control folder:
cd access-control
-
Start the services using Docker Compose:
docker-compose up -d
-
The access control service will run on port 9090
Database
PostgreSQL
Developers
Access Control Postman Collection
Supported Roles - To be implemented for role based access control
-
Data Owner (Business User):
- The individual responsible for datasets provided, authorizing which datasets will be shared, to whom, and for how long.
-
Data Consumer (Business User):
- The user who will have access to data for business-related tasks and decision-making processes.
-
Data Provider:
- Responsible for preparing, making available, integrating, and providing needed datasets/information to data consumers based on the directions of data owners.
- Technical role that implements data owner directions.
-
System Administrator:
- Responsible for the operation, management, and maintenance of the installed DATAMITE instance.
-
Security/Privacy Responsible:
- Responsible for setting privacy and security policies.
- Guides/consults users concerning related topics and oversees their policy implementation.
-
Data Governance Responsible:
- Develops, consults, monitors, and enforces data governance policies and practices, including Data Quality.
Roadmap and Functionalities:
- M13-M14: Requirements Analysis and Design
- M15: Keycloak Configuration
- M16-M18: User Authentication & Identity and Access Management
- M18-M20: Modify Keycloak Theme based on DATAMITE's UI