Added parser for Jackson3 by glascaleia · Pull Request #1032 · jwtk/jjwt

glascaleia · 2025-10-28T07:13:26Z

I created the new parser for jackson3. Regards Giuseppe

bdemers

Thanks @glascaleia this looks great

I left a handful of comments, but they are all small nits.

bdemers · 2025-10-28T15:25:09Z

+        <plugins>
+            <!-- The following plugin section is used in jjwt-jackson and jjwt-orgjson, to repackage (and verify)
+                 binary compatibility with previous versions. In v0.11.0 the implementations changed packages to
+                 avoid split package issues with Java 9+ see: https://github.com/jwtk/jjwt/issues/399 -->
+            <!-- TODO: remove these deprecated packages and this config before v1.0 -->
+            <plugin>
+                <groupId>org.apache.maven.plugins</groupId>
+                <artifactId>maven-shade-plugin</artifactId>
+                <configuration>
+                    <relocations>
+                        <relocation>
+                            <pattern>io.jsonwebtoken.jackson.io</pattern>
+                            <shadedPattern>io.jsonwebtoken.io</shadedPattern>
+                            <includes>io.jsonwebtoken.jackson.io.*</includes>
+                        </relocation>
+                    </relocations>
+                </configuration>
+            </plugin>


This looks like it was copypasta from the jackson2 module. It shouldn't be needed here as there is no backward compatibility concerns.

bdemers · 2025-10-28T15:26:08Z

+/**
+ * Deserializer using a Jackson {@link ObjectMapper}.
+ *
+ * @since 0.10.0


nit: use 0.14 (or {NEXT_VERSION})

bdemers · 2025-10-28T15:26:37Z

+     * @param objectMapper the objectMapper to modify by registering a custom type-converting
+     *                     {@link tools.jackson.databind.JacksonModule Module}
+     * @param claimTypeMap The claim name-to-class map used to deserialize claims into the given type
+     * @since 0.13.0


Suggested change

* @since 0.13.0

bdemers · 2025-10-28T15:27:17Z

+/**
+ * Serializer using a Jackson {@link ObjectMapper}.
+ *
+ * @since 0.10.0


See version comment above

bdemers · 2025-10-28T15:28:11Z

+ */
+public class Jackson3Serializer<T> extends AbstractSerializer<T> {
+
+    static final String MODULE_ID = "jjwt-jackson";


This probably doesn't matter at runtime but should this be jjwt-jackson3 to reduce confusion

bdemers · 2025-10-28T15:31:29Z

@@ -0,0 +1,146 @@
+/*
+ * Copyright (C) 2019 jsonwebtoken.io


Suggested change

* Copyright (C) 2019 jsonwebtoken.io

* Copyright (C) 2025 jsonwebtoken.io

bdemers · 2025-10-28T16:03:01Z

@@ -467,7 +473,7 @@
                <plugin>
                    <groupId>org.apache.maven.plugins</groupId>
                    <artifactId>maven-shade-plugin</artifactId>


Shouldn't need the shade plugin in this module (see comment above)

bdemers · 2025-10-28T16:03:54Z

            <properties>
                <maven.javadoc.additionalOptions>-html5</maven.javadoc.additionalOptions>
                <surefire.argLine>${test.addOpens}</surefire.argLine>
+                <easymock.version>5.6.0</easymock.version>


Should this be moved to the parent pom?

bdemers · 2025-10-28T16:05:16Z

This file should be removed (it would be in the root of the project if it needs to be added)

bdemers · 2025-10-28T16:05:22Z

This file should be removed (it would be in the root of the project if it needs to be added)

bdemers · 2025-10-28T16:13:44Z

Before merging, we need to finalize a plan for multi-jvm testing, Jackson3 (and likely other libraries in the near future) depends on Java 17.

We could build with 17+, and use multiple toolchains to test the other modules with older JVMs (e.g. Java 8).
Another option (which may work better with @bmarwell's #1021) could be to skip this module JVM > 8 (and require 17+ for releases)

NOTE: This is NOT something @glascaleia needs to worry about

glascaleia · 2025-10-29T05:57:36Z

I made the requested changes. Regards Giuseppe

glascaleia · 2025-11-05T05:47:05Z

@bdemers when the new release with this ??
Regards Giuseppe

Jaraxxuss · 2025-12-01T12:23:38Z

Good day, any updates?

lhazlewood · 2025-12-01T14:03:04Z

@Jaraxxuss sorry, we were on holiday last week and I had family obligations before that. I'll try to do a proper review this week. Sorry for the delay!

Jaraxxuss · 2025-12-02T08:37:36Z

@lhazlewood All good, thanks for the update!
Have a nice day

Jaraxxuss · 2025-12-02T08:38:29Z

+    </dependencies>
+
+    <build>
+        <plugins>


should it be used?

cj848 · 2025-12-08T22:04:25Z

I'm looking forward to seeing this PR completed and merged. Thanks for your efforts.

bhahn57570 · 2025-12-16T11:37:38Z

Question regarding the code:

If we follow the migration guide https://github.com/FasterXML/jackson/blob/main/jackson3/MIGRATING_TO_JACKSON_3.md they , they are changing the common ObjectMapper to JsonMapper.

Should we not do the same?

lhazlewood · 2026-01-08T00:12:59Z

We're still working on a plan forward. This PR duplicates code by coping it into a new module, but we'll likely need to consolidate both modules with a base jackson-core (or similar) module so test code and test cases are shared across both Jackson 2 and Jackson 3 modules to ensure we don't:

miss functionality across both
guarantee identical test cases/coverage so nothing slips through the cracks, and
don't have to maintain/duplicate code over time.

Additionally, I'd like the existing code in the jjwt-jackson module to be moved to a new jjwt-jackson2 module, and change the contents of the existing jjwt-jackson module to reflect the new Jackson 3 APIs.

This ensures that anyone already dependent on the jjwt-jackson module is upgraded automatically; we've seen more than a few projects just ignore or remain unaware of version upgrades otherwise. Anyone that wants to explicitly remain on Jackson 2 would then just change their gradle/pom dependency declaration to use jjwt-jackson2.

mistressxalexis

M

mistressxalexis

@

AindriuBrennan · 2026-03-05T15:07:27Z

Hi, when will Jackson 3 support be added?? It's now March 2026.

mparthasarathi · 2026-03-19T16:18:22Z

HI, Any timelines on when Jackson3 support likely to be available?

lhazlewood · 2026-03-20T14:26:25Z

Jackson 3 requires JDK 17 and we haven't made that a baseline yet, so it's a non trivial change for us at the moment. Because of this, we don't have a timeline.

timothyjward · 2026-03-31T18:17:11Z

Jackson 3 requires JDK 17 and we haven't made that a baseline yet, so it's a non trivial change for us at the moment. Because of this, we don't have a timeline.

Would it not be possible to make the Jackson 3 module build to a target of 17 while using target/release 8 for the rest of the build? That way people who want to use Jackson 3 (and therefore must use Java 17) can use the relevant module while others who want to use older versions of Java can use a different parser. It would just be a couple of properties in the parent pom and some overrides in the Jackson 3 module.

Also, if you are considering a change of baseline then Java 17 isn't exactly new...

mparthasarathi · 2026-04-27T15:21:55Z

Spring 3.5.x goes out of support by Jun'26. I was trying to use Jackson2 until JJWT is ready but it makes the whole migration more cumbersome and couldn't get it working. I wish we get Jackson2 support sooner than later

Added parser for Jackson3

4517ba2

bdemers reviewed Oct 28, 2025

View reviewed changes

PR jwtk#1032

e1d654a

Jaraxxuss reviewed Dec 2, 2025

View reviewed changes

Comment thread extensions/jackson3/pom.xml

</dependencies>

<build>

<plugins>

Copy link
Copy Markdown

Jaraxxuss Dec 2, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should it be used?

bdemers mentioned this pull request Jan 7, 2026

Add Jackson 3 Support #1038

Open

mistressxalexis reviewed Feb 10, 2026

View reviewed changes

FrankChen021 mentioned this pull request Feb 28, 2026

Upgrade to SpringBoot 4 and Spring Framework 7 FrankChen021/bithon#1165

Merged

	* Copyright (C) 2019 jsonwebtoken.io
	* Copyright (C) 2025 jsonwebtoken.io

Conversation

glascaleia commented Oct 28, 2025

Uh oh!

bdemers left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

bdemers commented Oct 28, 2025

Uh oh!

glascaleia commented Oct 29, 2025

Uh oh!

glascaleia commented Nov 5, 2025

Uh oh!

Jaraxxuss commented Dec 1, 2025

Uh oh!

lhazlewood commented Dec 1, 2025

Uh oh!

Jaraxxuss commented Dec 2, 2025

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cj848 commented Dec 8, 2025

Uh oh!

bhahn57570 commented Dec 16, 2025

Uh oh!

lhazlewood commented Jan 8, 2026

Uh oh!

mistressxalexis left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

mistressxalexis left a comment

Choose a reason for hiding this comment

Uh oh!

AindriuBrennan commented Mar 5, 2026

Uh oh!

mparthasarathi commented Mar 19, 2026

Uh oh!

lhazlewood commented Mar 20, 2026

Uh oh!

timothyjward commented Mar 31, 2026

Uh oh!

mparthasarathi commented Apr 27, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

10 participants

mistressxalexis left a comment •

edited

Loading