|
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 MihaelThis email and any files transmitted with it are confidential and intended
Schmidt
https://github.com/sitemule/ILEastic
Look particularly in
https://github.com/sitemule/ILEastic/tree/master/plugins/jwt
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.
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 copyright@midrange.com.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.