Skip to content

Conversation

@marktech0813
Copy link

@marktech0813 marktech0813 commented Nov 10, 2025

I added two convenience methods to expose decoded JSON without changing existing behavior. Now you can access both decoded header and payload directly from any DecodedJWT.

You can now use:

  • Decoded payload JSON: decoded.getPayloadJson()
  • Decoded header JSON: decoded.getHeaderJson()

Changes

Please describe both what is changing and why this is important. Include:

  • Endpoints added, deleted, deprecated, or changed
  • Classes and methods added, deleted, deprecated, or changed
  • Screenshots of new or changed UI, if applicable
  • A summary of usage if this is a new feature or change to a public API (this should also be added to relevant documentation once released)
  • Any alternative designs or approaches considered

References

Please include relevant links supporting this change such as a:

  • support ticket
  • community post
  • StackOverflow post
  • support forum thread

Testing

Please describe how this can be tested by reviewers. Be specific about anything not tested and reasons why. If this library has unit and/or integration testing, tests should be added for new functionality and existing tests should complete without errors.

  • This change adds test coverage
  • This change has been tested on the latest version of Java or why not

Checklist

I added two convenience methods to expose decoded JSON without changing existing behavior. Now you can access both decoded header and payload directly from any DecodedJWT.

You can now use:
- Decoded payload JSON: decoded.getPayloadJson()
- Decoded header JSON: decoded.getHeaderJson()
@marktech0813 marktech0813 requested a review from a team as a code owner November 10, 2025 16:21
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.

1 participant