You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We distribute the Tractus-X connector with a dataplane capable of handling both azure and aws related transfers. Despite including the azure provisioner in the controlplane runtime the AWS one is not included.
As a result the dataspace consumer AWS credentials are directly sent to the provider, as no temporary credentials (usually created during provisioning) are generated. This results in a potential security concern.
To Reproduce
Perform a TP using an AWS service (ex:S3).
Expected behavior
Creation of temp credentials instead of provider receiving the consumer's AWS credentials.
Possible Implementation
Include the AWS provision dependency in the edc-controlplane-base.
The text was updated successfully, but these errors were encountered:
This issue is dependent on this issue eclipse-edc/Technology-Aws#521 since is limited by the datadestination on upstream since it aims at allowing use provided credentials.
Describe the bug
We distribute the Tractus-X connector with a dataplane capable of handling both azure and aws related transfers. Despite including the azure provisioner in the controlplane runtime the AWS one is not included.
As a result the dataspace consumer AWS credentials are directly sent to the provider, as no temporary credentials (usually created during provisioning) are generated. This results in a potential security concern.
To Reproduce
Perform a TP using an AWS service (ex:S3).
Expected behavior
Creation of temp credentials instead of provider receiving the consumer's AWS credentials.
Possible Implementation
Include the AWS provision dependency in the edc-controlplane-base.
The text was updated successfully, but these errors were encountered: