Skip to content

Deprecate JwtParser#isSigned - #1055

Merged
lhazlewood merged 1 commit into
jwtk:masterfrom
arpitjain099:deprecate-jwtparser-issigned
Jun 7, 2026
Merged

lhazlewood merged 1 commit into
jwtk:masterfrom
arpitjain099:deprecate-jwtparser-issigned

Conversation

@arpitjain099

Copy link
Copy Markdown
Contributor

Per the discussion on #582, JwtParser#isSigned is a structural-only check slated for removal in 1.0. This marks it @Deprecated (interface + impl) with a @deprecated Javadoc note steering callers to parse directly and handle the exception, so anyone still using it gets a compiler/IDE nudge before 1.0 removes it.

Notes:

  • No behavior change; annotation and Javadoc only.
  • Nothing in JJWT's own codebase or tests calls isSigned, so there is no internal fallout, and failOnWarnings is false.
  • The Javadoc note is prose (no @link) so it is not coupled to a specific replacement method name.

Toward #582 (the actual removal would land in 1.0). Happy to adjust the wording or version note.

isSigned performs only a structural (not cryptographic) check and is
scheduled for removal in 1.0 (see #582). Mark it @deprecated on both the
interface and the implementation, with a Javadoc note steering callers to
parse directly and handle the exception instead of checking first.

Nothing in JJWT's own codebase or tests calls the method, so there is no
internal fallout.

Signed-off-by: Arpit Jain <arpitjain099@gmail.com>
@lhazlewood

Copy link
Copy Markdown
Contributor

Thank you!

@lhazlewood
lhazlewood merged commit 1ca444c into jwtk:master Jun 7, 2026
23 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants