Use proper claim types in JSON-RPC replay tool

[emlautarom1]

Changes

• Use the proper Claim type when building a JWT token in Kute.

Types of changes

What types of changes does your code introduce?

• Bugfix (a non-breaking change that fixes an issue)
• New feature (a non-breaking change that adds functionality)
• Breaking change (a change that causes existing functionality not to work as expected)
• Optimization
• Refactoring
• Documentation update
• Build-related changes
• Other: Description

Testing

Requires testing

• Yes
• No

If yes, did you write tests?

• Yes
• No

Notes on testing

Tested against a running Reth (TODO: document which version is being used)

Documentation

Requires documentation update

• Yes
• No

Requires explanation in Release Notes

• Yes
• No

[marcindsobczak]

Not sure if int or uint, probably both are fine. We were testing with uint master...fix/jwt_iat_type

[emlautarom1]

Not sure if int or uint, probably both are fine. We were testing with uint master...fix/jwt_iat_type

With ClaimValueTypes.UInteger64 Reth rejects the Authorization header since the iat claim is stored as a string. To debug this, run Kute and break before making the HTTP request, extract the Bearer token and paste it here: https://jwt.io/.

If you use ClaimValueTypes.Integer64 the iat claim is stored as an integer which Reth can deserialize.