Access Management with EDC & AAS - eclipse-tractusx/eclipse-tractusx.github.io GitHub Wiki
Description
Base Architecture of Catena-X
The Catena-X Data Ecosystem is based on several strategic components:
- Trusted Identity: Trust is established via verifiable credentials that proof the identity of a Catena-X participant. These credentials are managed in participant specific wallets
- Eclipse Data Space component: The EDC is to ensure sovereign data exchange between trusted business partners (aka Catena-X Participants) by verifying the consumer’s credentials and validating the bilateral agreement to the demanded usage policy
- Digital Twin Registry: Identifying the resource at which specific submodels of a digital twin can be obtained
- Submodel Server / Resource: These components provides access to the detailed attributes of a AAS submodel template. From a data space perspective, the implementation does not matter as long as the respective AAS API is being implemented, it does not necessarily need to be a submodel server component.
Goal
Demonstrating how this architecture can be reliable operated with a combination of Eclipse Dataspace Connector (Policies) and BaSyx (Roll-Based-Access-Control) considering Identification, Authentication and Authorization aspects. Ultimately, also performance would be a consideration as outlines in the chapter “Challenges”.
Business Scenario
A battery cell producer manufactures batteries for various different OEMs. The cells are delivered to the OEMs, where they are combined into battery modules/packs and finally assembled into a car. The battery cell producer wants to expose the digital twin of the produced battery cells over the Catena-X data space (via an EDC asset). So, they expose the actual battery cell submodel as well as a Digital Twin Registry on their side (Data Provider). Various OEMs (data consumers), who are registered and identified via Catena-X credentials (BPN, membership) are now going to retrieve battery cell information from the manufacturer. During data access it needs to be ensured that
- Only OEMs with an appropriate access and usage policy can access the digital twin registry
- OEMs can only access assets (battery cells) for their specific BPN (which has been shipped to them). They cannot retrieve batterie cell data of their competitors that were also manufactured at the same vendor. At this point, we are demonstrating the combination of EDC policies and AAS security based on BPN attributes (e.g.)
In the Tractus-X Session, the participants will be able to simulate different OEMS and experience the authentication and authorization behavior based on the concepts outlined above. Current Technology Challenges for future considerations Any mid-size car manufacturer produces ~500k BEV/PHEV vehicles per year. That's ~1.400 vehicles per day. Every vehicle has around 1000 battery cells that could be provided by one single supplier. That is 1,4 Million requests to a partner DTR with a lookup/shells request per day or approx. 16 requests per second. That supplier will have multiple customers so the number of requests might easily exceed 1,4 Million/Day. Furthermore, production is not necessarily running 24/7 so the 1,4 Million requests might not be distributed over 24 hours equally, but come in peaks of up to 1000 requests in a minute.
Responsible, Contact Person
- Thomas Obermeyer Lead Dataspace Architect, Catena-X
- Frank Schnicke Department Head Digital Twin Engineering, Fraunhofer IESE
- Christian Kosel Research Coordinator, ARENA2036
Prerequisites/Requirements
- Docker
- Postman/Insomnia
Challenges
this challenge, participants will be provided with a comprehensible Docker-based setup of the core infrastructure, including BaSyx AAS components, Keycloak, and digital twins of battery cells (including submodels). The goal is to configure a fine-grained access control model that exposes different levels of information to various stakeholders, such as plant operators and customers. Participants will learn how to: • Integrate Keycloak with the AAS infrastructure to implement access control (e.g., based on BPN). • Enable secure and policy-driven data sharing via the Eclipse Dataspace Connector (EDC) within a Catena-X data space. • Apply usage control and authorization policies to ensure that only authorized OEMs can access battery cell data relevant to their own BPN — preventing access to data from competing customers. By the end of the session, participants will experience a realistic simulation in which they take on the role of different OEMs and observe how access to the Digital Twin Registry and AAS submodels is controlled and restricted according to Catena-X identity and policy mechanisms.