-
Notifications
You must be signed in to change notification settings - Fork 186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error on SSO based on environment #1742
Comments
we are using waffle 1.9.1 |
Thank you for response. I will upgrade. Does the table of waffle versions that is compatible with window version exist? |
All versions of Waffle (should) work with all versions of Windows. The error from that doc file:
Looks like a problem with loading JNA, so the suggestion to try with a newer version of Waffle first that may have a newer JNA with a fix, is a good one. |
Thanks. |
@mciumac Which DLL specifically was missing? AFAIK Visual Studio C Runtime is not required with waffle/jna. @hazendaz I am surprised a VS C runtime would be required anywhere vs. Windows msvcrt.dll that is on all versions. Is this a recent change in JNA? A native DLL that was built against msvcrtXY? |
On arch level, they should support both still as it all still supports jdk8 and by extension both 32 and 64 bit.
Waffle is likely to go full jdk 11 and that's only 64 bit though. Many underlying pieces are jumping up so I expect that to continue given where java is now. Most likely will do one last java 8 then jump up.
Jna was using vc studio 2015 around that time for the build replacing some of msvc. Assuming given release notes it might have meant more. Msvc is also used still from what I could tell.
All in all safest bet is to get on 3.x of waffle as it should be otherwise drop in place and there were some larger issues fixed in jna 5 that had direct impact on waffle. That was likely at version 3 and release notes will state that. Many other items were fixed too so latest is most stable.
Sent from my Verizon, Samsung Galaxy smartphone
Get Outlook for Android<https://aka.ms/AAb9ysg>
…________________________________
From: Daniel (dB.) Doubrovkine ***@***.***>
Sent: Wednesday, October 12, 2022 6:25:22 PM
To: Waffle/waffle ***@***.***>
Cc: Jeremy Landis ***@***.***>; Mention ***@***.***>
Subject: Re: [Waffle/waffle] Error on SSO based on environment (Issue #1742)
@hazendaz<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fhazendaz&data=05%7C01%7C%7C566954b4ad614c4d006c08daaca0a771%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638012103410895930%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=N04OTsot7cgHEEv6iNcSnc6I%2Fs7VRm8T9%2B4YMJImA9A%3D&reserved=0> I am surprised a VS C runtime is required anywhere vs. Windows msvcrt.dll that is on all versions. Is this a recent change in JNA?
—
Reply to this email directly, view it on GitHub<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FWaffle%2Fwaffle%2Fissues%2F1742%23issuecomment-1276795447&data=05%7C01%7C%7C566954b4ad614c4d006c08daaca0a771%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638012103410895930%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=jEVS3uGE6toX6chN8RptDIvQGuGwhosMSpX5EfqIe3g%3D&reserved=0>, or unsubscribe<https://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAHODIY7MZ3XMCMLP4KVY43WC43FFANCNFSM6AAAAAARCTWDW4&data=05%7C01%7C%7C566954b4ad614c4d006c08daaca0a771%7C84df9e7fe9f640afb435aaaaaaaaaaaa%7C1%7C0%7C638012103410895930%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=w8yhpDPffzvc3bg8QcYWu6mxRfWo%2BdBtJc%2FNOFD6IFI%3D&reserved=0>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
ErrorSSO.docx
I have a Spring application that uses Spring Waffle SSO. In my dev environment I successfully access the application. But when deploying to Test environment I get the error (attached) when accessing application url. Both environment run WebSphere9.
The text was updated successfully, but these errors were encountered: