11-03-2026, 10:17 AM
I would like to renew this thread. We upgraded our production SaaS solution to the new migrated version on Sunday, but pretty quickly got reports from customers who were unable to log in. All of these were using Edge, and although not confirmed in all cases it looks like a common factor was that they used Edge for Business. It should be noted that my own Edge also says "Edge for Business" on the about screen but works without these issues, and we see in our logs that there are also a large number of successful login sequences with Edge. So most likely the issues is dependent on which security policies are enforced via Entra. As a temporary workaround we have turned off the security feature for changing sessionID totally (i.e. it is skipped regardless of browser at the moment). This is of course not an acceptable long-term solution for us.
Obviously there is some key difference between the IW versions mentioned above with regards to this, that makes some browsers non-compatible with the web application for the above cases. It would be much appreciated if you could analyse this and come back with an update the solves the issues, or suggest a better workaround than what I have been able to find so far.
A note: For the final case I have modified our code so that the Logout() call is made after rendering of the page is completed, as the above version could give issues on some pages.
Obviously there is some key difference between the IW versions mentioned above with regards to this, that makes some browsers non-compatible with the web application for the above cases. It would be much appreciated if you could analyse this and come back with an update the solves the issues, or suggest a better workaround than what I have been able to find so far.
A note: For the final case I have modified our code so that the Logout() call is made after rendering of the page is completed, as the above version could give issues on some pages.