Alert not been show in SEB

[markdem]

We have an exam system that will time an exam out after 5 min of inactivity (no idea why..). If I run the exam with SEB 2.2 the following message gets displayed.

We have recently updated the exam laptops we use and I installed the latest version of SEB (3.4.1) and now the message is not shown and the exam is closed when the timer runs out.
I have also tested this in Chrome (110.0.5481.78) and it also works fine.

Does anyone have any idea why it would not be shown under SEB?

Thanks

[dbuechel]

Could you please post the log file of the browser component (to be found under %LocalAppData%\SafeExamBrowser\Logs). You may also want to try to enable the developer tools of the browser and check the web console while an exam times out to see if there are any errors or alike.

[dbuechel]

Does your exam system work fine with any other Chromium-based browser? The difference between version 2.x and 3.x is exactly that we switched the browser engine from Firefox to Chromium.

[markdem]

Yes, I have also tested this in Chrome (110.0.5481.78) and it works fine. It is also the preferred browser by the vendor.

Is there anyway of turning on more logging to see what the SSL client is trying to connect to? The exam runs fine except for this one prompt and I don't see why it would need a separate connection for it.

Also, is there any easy way of switching back to firefox without uninstalling and reinstalling?

[dbuechel]

Is there anyway of turning on more logging to see what the SSL client is trying to connect to?

You could try to run your exam in the CEF sample application, see https://cef-builds.spotifycdn.com/index.html. That way, we could determine whether it indeed is an issue with the browser engine itself or not.

Also, is there any easy way of switching back to firefox without uninstalling and reinstalling?

No, SEB 3.x uses Chromium and likely won't ever revert to Firefox as browser engine.

[markdem]

I tried again using the CIF example app. Same thing, the pop up does not get shown..

I guess it is not a SEB issue in this case, but am wondering why it works fine in chrome?

Thanks for your help.

[dbuechel]

Yes, then it's definitely an issue with the browser engine. The reason is that CEF and Chrome are not exactly the same, they are both using the Chromium engine, but have a lot of different functionality around it.