-
Notifications
You must be signed in to change notification settings - Fork 7
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
ECDSA Keys #376
Comments
Will also close this one, if its still a problem, just let me know. E-Mail Quote: "We are happy to share with you that the DSC-to-DSC connection with DAT validation has been successful." [omejdn DAPS + PRODUCTIVE_DEPLOYMENT] |
I am reopening the issue as the quote above references certificates involving RSA. I am trying to use certificates with ECDSA (secp256r1) and the DSC keeps refusing them. Does the Dataspace Connector allow non-RSA algorithms? |
Reopened on request, my mistake, misunderstanding - sorry! We need to take a look. |
Currently we support signing of request tokens only with RSA, not with ECDSA, as can be seen in the following code snippet, see signing Line 354 in e13d25c
Is this requirement, to also enable ECDSA support necessary for you or does it work using the current standard solution RSA? |
I am trying to use the local Testbed CA provided certificate using ECDSA instead of RSA keys. as per new requirements. I adapted the conf/config.json with the new value for the keyStore, {ECDSA}.p12.
I am getting the following ERROR: An unhandled exception has been caught. [exception=(RSA signing keys must be RSAKey instances.)]
I tried changing the "ids:keyType" in conf/config.json from "RSA" to "ECDSA", but the issue remains. Is there anywhere else I must change further settings that I may have overlooked? I do not see any other value that may be changed in conf/config.json or application properties.
I have attached the logs below:
The text was updated successfully, but these errors were encountered: