FR-12 Subscribe to Relevant Events (2) #91
Description
Description:
The system shall allow each pool operator to subscribe to specific events from other pools that are relevant to its role and responsibilities (e.g., certificate updates, revocations, contract data changes).
Use Case:
A pool wants to be notified about contract or certificate events related to one of its customers, even if that event was triggered in another pool.
Current Status
This is flagged as possible in OPNC v1.0.
Implementation appears to be handled via a webhook service, but specifics regarding scope, filtering, and authorization need clarification.
This use case has interoperability relevance (IOP) and is supported in principle.
Assessment:
The concept is already in place through webhooks, but access control and filtering rules need to be made explicit to ensure data is not over-shared.
This is a technically feasible requirement, but will require clear governance, standardized filtering, and consistent behavior across implementations.
Discussion Points
- Should OPNC define a standard event subscription and delivery format?
- How do we implement fine-grained access control at the event level?
- What event filtering parameters should be mandatory (e.g., by customer ID, OEM, CPO)?
- Is this addressed via code or via documentation,or both?