Authentication process

[jes14]

Hello Community,

I found out that it's called "Connector-as-a-Service". so I want to know more details about the authentication process in this context.

How is the authentication process in this EDC with other EDC in the dataspace?

Thank you very much.

[richardtreier]

Hi @jes14,

authentication in EDC can be distinguished into:

• User Identity and Access Management (IAM) that decides who can access your connector.
• Connector Identity and Access Management (IAM) that decides data space participants and secures all communication between connectors. Connector IAM is realized via Data Attribute Provisioning Services (DAPS), which are defined by the Core EDC.

We add our own extensions to the Core EDC, so our EDC is compatible to other EDCs.

Connector-as-a-Service (CaaS)

Sovity (Website | LinkedIn | Contact) offers its customers the Connector-as-a-Service (CaaS), hosted and maintained by sovity:

• Decide who can access your Connector. Decide who can access your Connector API.
• We configure your Connector to work in a given data space with your certificate and details or have your data space secured by our hosted and managed sovity DAPS.
• Access the Management Portal for your EDC Connector (metrics, logs, etc.).
• Access the Connector itself (UI & API).

Community Editions

Our Community Editions can be found in sovity/edc-ui and sovity/edc-extensions:

• Quickly start a slim version of our extended EDC on your local machine.
• Showcases most of our ongoing work on extending EDC Functionality.

However:

• To secure a potential production EDC Connector, you'll need to handle all authentication and authentication related configuration yourself, in addition to infrastructure concerns and general EDC configuration.

Does this answer your questions?

[jes14]

Hi @richardtreier
I see. Yes, it does. Thank you for the information.