It is no longer possible to reproduce the bug across Firefox, Chrome, Edge and Safari. My test have not shown any other problems in internal or external web. Actually the system seems much faster now. Good work

Like agreed upon on today's meeting we will go for the long term solution.

I can reproduce the page reload issue in a fresh installation of Firefox.

None of the configuration settings tried have yielded a consistent change for the experience.
We are out of smaller adjustments to try

There is a different experience in different browsers for different users and it seems to be related to which is handled differently in the different browsers

• Copenhagen report it works in Chrome, but reloads page in Edge, with no changes to exceptions settings. (short term solution explained below)

• Anne-Marie reports it reloads in Edge and Chrome, but if she configure them to use the exceptions settings, then works as it should.

• Jesper experience reload all the time in Chrome, Edge and Opera no matter if the exceptions settings are there or not.

• Mogens has the issue in Firefox but not in Edge or Chrome, no exception settings.

• I have noticed different behaviors at different time.

  • FireFox reloads, except if I configure the trust settings, then it works as expected.

  • Edge works on my machine, it reloads on the management server (jump server) in the hosting environment

  • Chrome works

  • Opera works
    
    

I've looked into a short term solution and discussed a more long term solution with

Short term solution could be to add the Valghalla site and access control site to cookie exceptions in the browser, ex. for FireFox as in the screenshot below.

for staging it would be test-korsbaek-adm.os2valghalla.dk and adgangsstyring.eksterntest-stoettesystemerne.dk
for prod <municipal-adm>.os2valghalla.dk and adgangsstyring.stoettesystemerne.dk

This setting could make it a more fluent experience because it will allow the refresh of cookies to run without page load.

A long term solution should could be to do major adjustments to the login process so it will use JWT against the frontend instead and SAML in the backend.
Core functionality wise there should be no difference, but it should eliminate the page reload issue and the third party cookie handling issue at the same time.
will investigate and give an estimate on the work needed.

as I see it with the investigations I’ve done and the feed back from municipal I don’t see another way around than to deal with this sooner than later, but please let me know if you disagree

I have not, I can ask them, but I expect more or less the same answer as when we started, they will point to the documentation (.NET classic) and politely ask us to figure it out on own.
But I can surely ask them again.

Just a thought - did you try asking KOMBIT at some point what kind of solution they recommend for this problem? Should we look for other systems using FK Adgangsstyring and their solution?