Upgrade to WebAuthn4J 0.31

[tsegismont]

Describe the feature

To keep up with WebAuthn evolutions, we should upgrade WebAuthn4J to 0.31+

We had to ignore a test that cannot pass without this version: #747

There are a couple of constraints. WebAuthn4J 0.31+ requires:

• Java 17, see Update baseline JDK version to 17 webauthn4j/webauthn4j#1221
• Jackson 3, see Upgrade to Jackson3  webauthn4j/webauthn4j#1222

[tsegismont]

Any comments @vietj @FroMage @ynojima ?

This would be a breaking change, but that sound reasonable to me.

[ynojima]

Because the Jackson 3 migration required it, WebAuthn4J 0.31 and later use JDK 17 as the baseline.
If needed, it would be possible to continue maintaining WebAuthn4J 0.30.x for JDK 11 a little longer and backport webauthn4j/webauthn4j#1318, which addresses the issue causing the MDS-related tests to fail.
However, when do you expect vert.x to move to JDK 17 as its baseline?

[tsegismont]

We'll move to JDK 17 or later in Vert.x 6, I think.

Thanks for your proposal. AFAIC, we could use Maven toolchains to build vertx webauthn4j with JDK17. We already do that for a few other modules in the stack.

[ynojima]

Because of issues related to the Jackson 3 migration, Quarkus also needed a release on the 0.30.x line, which still uses Jackson 2. So I released WebAuthn4J 0.30.3.RELEASE.
https://central.sonatype.com/artifact/com.webauthn4j/webauthn4j-core/0.30.3.RELEASE/dependencies
quarkusio/quarkus#53709

Updating to this version first should work as a workaround for the FIDO MDS-related issues.

[tsegismont]

Thanks for the heads-up @ynojima !

I just sent #749 that allows to re-enable the ignored test.