JWT Decoding Processor#400
Conversation
Benchmarks clangBenchmark execution time: 2025-05-02 14:54:56 Comparing candidate commit 50f86d5 in PR branch Found 1 performance improvements and 0 performance regressions! Performance is the same for 0 metrics, 0 unstable metrics. scenario:global-benchmark.random.clang
|
Benchmarks clang-pgoBenchmark execution time: 2025-05-02 15:11:07 Comparing candidate commit 50f86d5 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 1 metrics, 0 unstable metrics. |
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #400 +/- ##
==========================================
- Coverage 85.21% 85.09% -0.12%
==========================================
Files 166 169 +3
Lines 8364 8600 +236
Branches 3687 3777 +90
==========================================
+ Hits 7127 7318 +191
- Misses 477 497 +20
- Partials 760 785 +25
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
… anilm3/jwt-decoder
This PR introduces a new processor for decoding JWT tokens. This new processor can be used as a preprocessor to generate an address containing the JWT token contents as a map with the following schema:
{ "header": { ... }, "payload": { ... }, "signature": { "available" : true | false } }In addition, the following supporting changes have been introduced:
base64_decodetransformer has been "forked" into thebase64url_decodetransformer, as used by JWT.Related Jiras: APPSEC-57472