​Hello,

we have an mobile based app (iOS) that cannot decode id_token issued by ISAM. This is because ISAM generate the id_token base64 string without padding ("==") at the end.

Can this behaviour of ISAM changed?

Regards,
Juergen

------------------------------
Jürgen Hitt
------------------------------

Hello Juergen,

The 'id_token' which is a JWT is 'Base64 URL Encoded' as opposed to 'Base64' encoded. There is a little bit of a difference and you can't just select the whole JWT and base64 decode it.

A JWT is made of 3 separate base64 encoded sections with '.' characters between them.

------------------------------
JACK YARBOROUGH
------------------------------

Hi Jack,

I was not aware of this difference. Makes pretty much sense. I will give this info to our App developers.

Thanks!

------------------------------
Jürgen Hitt
------------------------------

Original Message:
Sent: Wed January 22, 2020 12:17 PM
From: JACK YARBOROUGH
Subject: Decoding issue ISAM id_token

Hello Juergen,

The 'id_token' which is a JWT is 'Base64 URL Encoded' as opposed to 'Base64' encoded. There is a little bit of a difference and you can't just select the whole JWT and base64 decode it.

A JWT is made of 3 separate base64 encoded sections with '.' characters between them.

------------------------------
JACK YARBOROUGH
------------------------------