- capture both RequestHash and ConfigKeyHash from the request headers and use both to validate the request. This enables to choose to just enforce the plain conf, instead of the whole conf+binaries combination, which is platform-specific - support storing multiple keys, required e.g. to support multiple platform-specific keys - make suppling of the config file optional - extend automated tests to cover new features - clanup redundant index - return config file using its stored filename
via the API is possible to associate a Safe Exam Browser configuration and its validation key to the proctored object. The proctored page will then take care of enforcing that, if the safe exam browser is in use, the supplied request header matches with the configuration and the URL. When such match fails, we now return the configuration file to the browser, so that users can open it and restart their session properly configured.