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
When starting the EDC the OAuth2Extension.getEncodedClientCertificate always throws an org.eclipse.dataspaceconnector.spi.EdcException: Public certificate not found exception.
Expected Behavior
Connector starting and resolving certificates from vault
Observed Behavior
Connector not starting
Steps to Reproduce
Steps to reproduce the behavior:
Start IDS Connector
Context Information
Add any other context about the problem here.
Used version 0.0.1-20220818-SNAPSHOT
Detailed Description
Extension is always using the NoopCertificateResolver
Possible Implementation
Probably the DefaultCertificateResolver should be used instead
With our custom extension everything works fine. Our problem occurs with the Azure Vault extension from this repository, but I assume the HashiCorp vault extension from this repository has this problem, too.
But I just saw that you fixed this issue 7 days ago in PR #1842 -> will close this issue.
Bug Report
Describe the Bug
When starting the EDC the
OAuth2Extension.getEncodedClientCertificate
always throws anorg.eclipse.dataspaceconnector.spi.EdcException: Public certificate not found
exception.Expected Behavior
Observed Behavior
Steps to Reproduce
Steps to reproduce the behavior:
Context Information
Add any other context about the problem here.
Detailed Description
NoopCertificateResolver
Possible Implementation
DefaultCertificateResolver
should be used insteadDominik Pinsel [email protected], Mercedes-Benz Tech Innovation GmbH, legal info/Impressum
The text was updated successfully, but these errors were encountered: