Re: Qc3VerifySignature to verify a JWT

One thing you have to make sure is to provide the right key length. I was
having a bad time with the Qc3CalculateSignarute API, and after so many
disappointing attempts I realized that not only the key length was the
problem, but also I had to fill out the trailing bytes with zeroes. That
solved my problem.

JS


El mié, 9 ago 2023 a las 7:15, Brian Garland via MIDRANGE-L (<
midrange-l@xxxxxxxxxxxxxxxxxx>) escribió:

Niels,

Thanks for the response. The ILEastic code and my previous test code
basically did the same thing. Using either I still get Qc3VerifySignature
telling me it is an invalid token. I have verified the token using
JWT.io. Any thoughts on what could be going wrong?

Brian

On Fri, Aug 4, 2023 at 4:14 AM Niels Liisberg <nli@xxxxxxxxxxxxxxxxx>
wrote:

We have already done that in the ILEastic project. Thanx to Thanx Mihael
Schmidt

https://github.com/sitemule/ILEastic

Look particularly in

https://github.com/sitemule/ILEastic/tree/master/plugins/jwt

--
This email and any files transmitted with it are confidential and intended
solely for the use of the individual or company to whom they are
addressed.
Do not disclose, distribute, or copy this email to others outside your
company. If you have received this email in error, please notify the
sender
immediately and delete this email from your system.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxxxxxxxxxx for any subscription related
questions.