Quiz

In our testing, the Config Key (CK) and Browser Exam Key (BEK) checks seem to still work with current SEB for Windows versions. There are two known issues when these checks don't work:
- You cannot use Moodle embedded in an iFrame in another web platform (via LTI) with the CK and BEK.
- If your Moodle server/network configuration changes the URL of your Moodle site, the CK and BEK checks won't work. The keys are hashed with the URL of each HTTP request (web page/resource URL) on both the server (in Moodle) and on the SEB clients and the resulting value is transmitted from the client and compared to the value in the Moodle server. So if the URL of your Moodle site is different for the SEB clients than for the Moodle server, the check cannot work. Apparently this can happen for example when using a web proxy (see this reported issue):

"i've a url in the form of www.domain.com/prefix/moodle-urls, the proxy removed "prefix" so moodle server didn't know about it.
I solved this by turning off the proxy rewrite url and putting moodle inside a folder called prefix so that the full url matched the server file structure, i also turned off the $reverseproxy options in moodle config.php"

There might be other Moodle server or network configurations which change the URL, make sure to configure your systems correctly. Also students might be using some network/anti-malware analyzing tools which theoretically could change the URLs of Moodle pages for the SEB client (if only some students have that issue with the CK/BEK).

Let us know if you find a solution to your individual problems, as we could then think about mitigating against such problems in future SEB versions. Also for making sure that some SEB version doesn't have a bug relating the CK/BEK check, try it also with the macOS or iOS version (you can use any iPad or iPhone with iOS 11 or newer to try it out quickly, even if you don't have Macs).