@@ -10,14 +10,14 @@ Each component is separated into different namespaces and all communications bet
Apart from the communication between components, there are 2 other entities that can use them:
-**Admin/superadmin**: Responsible for managing users with the Register or carrying out special operations in the CCF.
-**Users**: They are those who want to use CAPIF, registering as a user in the Register and as Invoker or Provider in the CCF.
-**Admin/superadmin**: Responsible for managing users with the Register or carrying out special operations in the OpenCAPIF Core.
-**Users**: They are those who want to use CAPIF, registering as a user in the Register and as Invoker or Provider in the OpenCAPIF Core.
## **Vault NS**
This namespace belongs to Vault.
This component is responsible for managing all CAPIF certificates, so other components such as the Register or the CCF communicate with it to create new certificates or request keys.
This component is responsible for managing all CAPIF certificates, so other components such as the Register or OpenCAPIF Core communicate with it to create new certificates or request keys.
## **OpenCAPIF NS**
@@ -42,17 +42,17 @@ This component will expose a URL at K8s ingress to access it.
Te OpenCAPIF Component consists in X services, each one related with one API:
-**CAPIF Discover Service**
-**CAPIF Publish Service**
-**CAPIF Events Service**
-**CAPIF Invoker Management Service**
-**CAPIF Security Service**
-**CAPIF Logging Service**
-**CAPIF Auditing Service**
-**CAPIF Access Control Policy Service**
-**CAPIF Provider Management Service**
-**CAPIF Routing Info Service**
-**CAPIF Open Discover Service**
-**CAPIF Discover Service**: Allows API invokers to search for and discover published APIs based on query filters, retrieving API metadata and interface information.
-**CAPIF Publish Service**: Allows API providers to publish, update and unpublish their APIs in the CAPIF Core, making them discoverable to authorized invokers.
-**CAPIF Events Service**: Enables API invokers to subscribe to CAPIF events. It supports event subscription and unsubscription and can optionally send event notifications.
-**CAPIF Invoker Management Service**: Handles onboarding and offboarding of API invokers, including registration of invoker profiles and management of their status.
-**CAPIF Security Service**: Acts as the access control point of the CAPIF Core, validating API invocations and enforcing authorization policies.
-**CAPIF Logging Service**: Intercepts and stores logs of API invocations for monitoring, troubleshooting and compliance purposes.
-**CAPIF Auditing Service**: Provides audit capabilities for service API invocations to support accountability and traceability.
-**CAPIF Access Control Policy Service**: Manages access control policies that define which API invokers can access which published APIs and under what conditions.
-**CAPIF Provider Management Service**: Handles registration and management of API providers, including their profile and the APIs they own.
-**CAPIF Routing Info Service**: Provides routing information to API invokers, so they can locate the correct API Exposing Function (AEF) endpoint for a given published API.
-**CAPIF Open Discover Service**: Enables API invokers external to the CAPIF domain to discover published APIs, for use in interconnection scenarios.
-**Helper Service**: Service that simplifies integration with third parties such as external management portals.
Also this component deploys some side services:
@@ -62,7 +62,3 @@ Also this component deploys some side services:
-**Celery**: This component is responsible of send event messages when eventReq feature is active.
-**CAPIF DB**: CAPIF database, where all information related to CAPIF services such as invokers, registered providers or published services is stored.
## **New Architecture**
You can check the details of all these changes in the conversation on the [OCF wiki](https://labs.etsi.org/rep/ocf/community/-/wikis/New%20architecture).
