×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
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
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
