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
I found that a similar topic was discussed in issue #33, but it seems like the JCA standard decided to not continue the same naming pattern - presumably because, as noted in #33, EdDSA instantiations already include a choice of a particular hash algorithm.
Anyway, it might be worth considering to align with the standard JCA names to improve interoperability.
The text was updated successfully, but these errors were encountered:
Hi! I recently looked into testing the compatibility between Yubico/java-webauthn-server and ed25519-java, and I quickly ran into a small issue: the JCA provider algorithm names differ from those used in OpenJDK 15. Specifically, OpenJDK does not include the hash algorithm in
Signature
names, while ed25519-java does. See: Java Security Standard Algorithm Names (Java SE 15)I found that a similar topic was discussed in issue #33, but it seems like the JCA standard decided to not continue the same naming pattern - presumably because, as noted in #33, EdDSA instantiations already include a choice of a particular hash algorithm.
Anyway, it might be worth considering to align with the standard JCA names to improve interoperability.
The text was updated successfully, but these errors were encountered: