[IDM.OCM.E1.00010] TSA Acception

The Connection Manager MUST use TSA to accept/block connections automatically according to the incoming DID.

TSA policy manager to be included for the linked auto revocation / auto renewal services as described in the TSA policy manager readme: https://gitlab.eclipse.org/eclipse/xfsc/tsa/policy

Integration of TSA Policy Manager: Assume it is running as external Microservice and must be called by OCM (also see: https://gitlab.eclipse.org/eclipse/xfsc/tsa/policy/-/blob/main/doc/policy_development.md?ref_type=heads) -> POST call to PDE (Policy Decision Endpoint: https://gitlab.eclipse.org/eclipse/xfsc/tsa/policy/-/blob/main/doc/policy_development.md?ref_type=heads#policy-development-extensions) -> POST Call to PDE must forward the did url - see DID integration below:

Integration of DID: Incomming Connection refers to a DID, while DID must be used to forward the DID relation to the TSA policy manager for evaluating the accept/ block policy. Consumers of the OCM will be responsible to set up the policy and configure the PDP url for the responsible TSA instance.