Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

data-plane requires public and private key settings also if not really needed #4407

Closed
ndr-brt opened this issue Aug 12, 2024 · 0 comments · Fixed by #4408
Closed

data-plane requires public and private key settings also if not really needed #4407

ndr-brt opened this issue Aug 12, 2024 · 0 comments · Fixed by #4408
Assignees
Labels
refactoring Cleaning up code and dependencies

Comments

@ndr-brt
Copy link
Member

ndr-brt commented Aug 12, 2024

Bug Report

Describe the Bug

Currently to start a data-plane is always mandatory to provide private and public key configuration through settings:
edc.transfer.proxy.token.signer.privatekey.alias
edc.transfer.proxy.token.verifier.publickey.alias

but they are only needed if the data-plane provides PULL transfer mechanism

Expected Behavior

to not require them in case of no PULL transfer mechanism is registered

Observed Behavior

exception at startup

Steps to Reproduce

build a barebone data-plane runtime and run it

Context Information

EDC 0.8.1

Detailed Description

If applicable, add screenshots and logs to help explain your problem.

Possible Implementation

You already know the root cause of the erroneous state and how to fix it? Feel free to share your thoughts.

@ndr-brt ndr-brt added bug_report Suspected bugs, awaiting triage triage all new issues awaiting classification labels Aug 12, 2024
@ndr-brt ndr-brt self-assigned this Aug 12, 2024
@ndr-brt ndr-brt added refactoring Cleaning up code and dependencies and removed bug_report Suspected bugs, awaiting triage triage all new issues awaiting classification labels Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
refactoring Cleaning up code and dependencies
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant