Hey there,
after trying to find an answer in this thread (JWT.io different result compared to base64decode.org) I realized that this is a different issue.
Preface: I blackened the sensible data.
This is the raw JWT header as it is logged by the creator application:
{
“alg”: “RSA256”,
“subject_name”: “”,
“issuer_name”: “”,
“serial”: 1841657277971189406
}
This is the JWT header as it is decoded by JWT.io:
{
“alg”: “RSA256”,
“subject_name”: “”,
“issuer_name”: “”,
“serial”: 1841657277971189500
}
This is the JWT header as it is decoded by Base64 Decode and Encode - Online
{
“alg”: “RSA256”,
“subject_name”: “”,
“issuer_name”: “”,
“serial”: 1841657277971189406
}
As you see, the serial is decoded different.( …500 | 406) where the …406 ending is the correct value.
When using a string as dataType it is parsed correctly but the corresponding party expects a number.
As I get an error response (500) and am currently not able to get more information from there.
Maybe someone can clarify why this is happening.
Thank you in advance
Ray