RE: base64 URL decode - for jwt

I’ve not needed to look into base64url for the purposes of decoding a jwt ticket.

So not really sure what he would need that for.

In my process I just use http_persist_req() and get back the raw response and then parse the jwt info out of it.


--
Chris Hiebert
Lead Software Developer
Disclaimer: Any views or opinions presented are solely those of the author and do not necessarily represent those of the company.

From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of Vern Hamberg via MIDRANGE-L
Sent: Monday, March 10, 2025 8:20 PM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: Vern Hamberg <vhamberg@xxxxxxxxxxxxxxx>
Subject: Re: base64 URL decode - for jwt


Hi Chris



As I understand it, and I think Jay mentioned it, the so-called BASE4

part is actually BASE64URL - this replaces a couple things in BASE64

that don't work in URLs - like a forward slash, I believe. I forget, but

I looked it up.



--



*Regards*



*Vern Hamberg*



IBM Champion 2025 <cid:part1.yF3xcJ7F.stqK4olY@centurylink.net<mailto:part1.yF3xcJ7F.stqK4olY@xxxxxxxxxxxxxxx>> CAAC

(COMMON Americas Advisory Council) IBM Influencer 2023