We have an integration from an installed win32 application my https://my.shiprush.com It's been working for a few years now.
In the past few days, customers are reporting that when they try to ship using our integration, they get the shiprush logon page, but after they enter their credentials, they are redirected back the the logon page.
The integration works by calling a PHP script on a server, and passing in all the shipping details. This script calls shipRushClient.Open after loading the shipment JSON object with the details. At this point, the user would see the logon page, or the shipment page if they were already logged on. Now, they get stuck in a loop entering their logon credentials. If they open myshiprush directly, they can log in with no problems.
https://www.screencast.com/t/7CadX66Ogo
I can email the actual PHP/Javascript code to support if they want to see how we're doing it.
I know Chrome is enabling samesite cookie checks in 80, but we see the same behavior when testing with IE, which is not Chromium based. The samesite cookie checks seem like they may be related, but we're not sure.
We've testing using Incognotio mode to remove cached details/cookies/etc, and we see the same behavior.
In the past few days, customers are reporting that when they try to ship using our integration, they get the shiprush logon page, but after they enter their credentials, they are redirected back the the logon page.
The integration works by calling a PHP script on a server, and passing in all the shipping details. This script calls shipRushClient.Open after loading the shipment JSON object with the details. At this point, the user would see the logon page, or the shipment page if they were already logged on. Now, they get stuck in a loop entering their logon credentials. If they open myshiprush directly, they can log in with no problems.
https://www.screencast.com/t/7CadX66Ogo
I can email the actual PHP/Javascript code to support if they want to see how we're doing it.
I know Chrome is enabling samesite cookie checks in 80, but we see the same behavior when testing with IE, which is not Chromium based. The samesite cookie checks seem like they may be related, but we're not sure.
We've testing using Incognotio mode to remove cached details/cookies/etc, and we see the same behavior.