-
|
Hey, I want to test the new screen proctoring feature but I can't get it to work. I did the following:
I am not sure what exactly the problem is. Does the user have to be in Status Active to monitor the screen? On https://seb-server.readthedocs.io/en/latest/screen_proctoring.html#gallery-view it states "When a SEB is connected to SEB-Server and the user is logged into LMS, a tile with the latest screenshot will appear.". So does a user need to log into an LMS to change Status to Active? Kind regards, |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 11 replies
-
|
Hi, Unfortunately, Mock-up Exams will not work with Screen Proctoring because they don't have an Assessment Tool login. For all Exams with Assessment Tool, the Assessment Tool login is the trigger for a SEB connection to get scheduled for a Screen Proctoring room. But you can create an Exam without Assessment Tool (right in the Exam list page) and configure it for Screen Proctoring as you have done before. For this kind of Exams no Assessment Tool login should be needed and SEB Server should schedule a SEB connection to Screen Proctoring right after the status of the connection is ready. Best Regards |
Beta Was this translation helpful? Give feedback.
-
|
Hi,
Indeed interesting, usually SEB should use the device internal Unix timestamp to stamp a screenshot and this should be independent of local time zone settings. Also, all timestamps in the database are always stored as Unix timestamp (milliseconds since 00:00:00 [UTC] on 1 January 1970). For proper understanding of mine,, the local time was wrongly set in the device where SEB was running on or on the device where the screen proctoring was shown? In the second case, we will have a closer look at the screen proctoring and GUI slide component, in the first case we will need to have a closer look at the SEB client and the timestamp it uses. Thanks for the information.
The logs show an DB integrity violation, most probably as a subsequent error because the Exam on the screen proctoring database has not been created. Interesting would also be a few logs before, maybe there were Warnings or Errors before?
This was definitely the wrong approach, since all "id" columns in the database are auto-generated by the database itself. So "id" is an integer given by the database while "uuid" is an alphanumeric unique identifier given by the system (SEB Server) or in case of the Exam, the id if the exam given from the LMS. In your case (Olat) this might also be a integer number but of other LMS it is not and for Exams without LMS it is an alphanumeric UUID. This might cause other problems then.
This might be caused by the former action of using the uuid also as is. But I don't know for sure.
It depends on the Olat system. If you use OpenOlat, then we d no have a SEB Server integration for that Assessment Tool yet. Only for Olat developed by UZH we have a cooperation and proper integration with SEB Server. For Open Olat some features might work since the integration uses core API whenever possible but, as I remember correctly, not for the Login and User Name resolving. Probably the best way to go is to first solve the problem to apply screen proctoring to an Olat Exam without errors and without the need to manually change the database entries. If you try this again and send us both whole logs, from SEB Server as well as from Screen Proctoring Server, we can take a look into it and might find the problem. |
Beta Was this translation helpful? Give feedback.
-
|
Hi again, I most probably have located the Issue with Olat and Screen Proctoring that you describe above. I remember that the screen proctoring, on one point, needs to distinguish on a given identifier on whether it is an id or an uuid. And since uuids usually are alphanumeric, except in the case of Olat course/quiz identifiers, I think screen proctoring get it wrong now and interprets the uuid as an id. This would also explain the behaviour you described of when you used the uuid also as id in the database but will not entirely fix the issue. I will check and correct this as soon as possible and make a bug-issue out of this issue to track. If this is okay with you, I will come back to you as soon as I have fixed the problem and prepared the patch, with further instruction on how to pull the patch on you site. Best regards |
Beta Was this translation helpful? Give feedback.
-
The time was wrongly set on the device where SEB was running. I checked it again by setting the time of the clock manually to a future time. I did not alter the timezone. In the table screenshot_data of the DB SEBScreenProctoring the timestamp was set to the time that I set manually on the device where SEB was running.
1737454390687 is Tue Jan 21 2025 10:13:10.687 but in reality it was more like 10:01.
So you don't need me to provide log files as you mentioned in your first reply?
I will gladly help you with that. Also thanks for the great support! Kind regards, |
Beta Was this translation helpful? Give feedback.
-
|
Hi Stefan,
If you have changed the OS system clock itself, I think we cannot do mutch about it, but if you changed the OS display time, it should not affect the OS system clock itself and the Unix timestamp that is defined to be used by SEB. Can you just tell us what SEB client you use SEB Windows Version or SEB MacOS Version or SEB iOS Version? So we can try to replicate the behaviour locally.
Not at the moment thanks, maybe later if the fix is not working as expected. Best |
Beta Was this translation helpful? Give feedback.
-
|
Hi Andreas,
I changed the time in the Date and time settings menu under Additional clocks. Method 1: https://www.geeksforgeeks.org/how-to-change-the-time-in-windows-11/ Kind regards, |
Beta Was this translation helpful? Give feedback.
-
|
Hi Stefan Now I managed to have a look at this and was able to apply a fix that hopefully makes Screen Proctoring work with Olat. I prepared a patch for you, so you can test this on your site properly. First you need to fetch the patch. I assume you have a normal docker-compose based setup, not a Kubernetes setup right? to pull and run the new patch you need to:
Now you can test if Screen Proctoring works new with Olat. You should start this and import a very new Test/Exam for that because the data of the old Exams are most probably invalid. If everything works fine, please tell us, then I can apply the fix also for the current development. And if there are other issues, please add also the logs of both backend services, "seb-webservice" and "sps-webservice" for further analyses. Best regards |
Beta Was this translation helpful? Give feedback.
-
|
Hi Andreas, thanks for the instruction. I can now enable screen proctoring to an Olat Exam without the original error but still can't use it. I think the issue relies with the missing implementation of the Restriction API. So your fix worked. Best regards, |
Beta Was this translation helpful? Give feedback.
-
|
Hi Stefan Thanks for testing. I'm not sure if the missing SEB Restriction error is related to Screen Proctoring. But it seems at least that your Olat system doesn't have full SEB Server support yet. In the logs I can see, that you have tried to apply the Test Run for the Exam and this failed due to lack of SEB Restriction Settings on Olat. So you were not able to apply the Test Run right? Or was the Test Run applied anyway but with that error? If you are able to open the Exam in Monitoring view and connect with a SEB client and login to Olat, Screen Proctoring should be applied (even without SEB Restriction). If this is not the case, please, can you describe what happens when SEB client connects and login to Olat? Are there some errors at that time in the SEB Server log or in the SEB client logs? And can you please check beforehand that Screen Proctoring is also enabled within the Exam Configuration of the Exam. Otherwise SEB client will not send Screenshots even if SEB Server has created a session for SEB client on the Screen Proctoring service.
Best regards |
Beta Was this translation helpful? Give feedback.
-
|
Hi Andreas,
The Test Run was applied anyway. I forgot to add a log of sps_webservice when applying the test run in my last answer.
Client: When I open the exam connection configuration I get a message that the screen will be proctored. After accepting the browser gets redirected to the login page of our OLAT instance. After logging in the browser redirects to the course with the exam (same Exam URL that is visible in SEB-Server Exam page). In the taskbar below there is the screen proctoring symbol but it's not green. Server: When accessing the monitoring under running exams. I see the exam and the connected user in state Ready. When accessing screen proctoring via "View exam" there is the message: "No live sessions available". When the SEB client connects and logs into Olat there are no logs in the SEB-Server. Client logs: Browser log is empty but I thought maybe that can also be a useful information. Because of the logs I checked the table oauth_access_token and the entry seems weird for me.
I did enable this option because it is described in your documentation https://seb-server.readthedocs.io/en/latest/screen_proctoring.html. Kind regards, |
Beta Was this translation helpful? Give feedback.
-
|
Hi Stephan, Thanks for the detailed information. For me now, it is relatively clear that screen proctoring doesn't work with Olat because your Olat instance do not have full SEB Server integration support. As far as I know, only the Olat developed by UZH has full SEB Server integration yet. They tried to rely on standard API calls as best as possible, but not every feature was able to be implemented with the standard API but needed an extension. Namely, the SEB Restriction feature as well as the Login and Name Resolving feature. The second one is essential for screen proctoring, since only when SEB detects a LMS login, it sends the user identifier to SEB Server this will trigger name resolving in one hand and the screen proctoring group scheduling on the other hand. Also the SEB connection within the SEB Server monitoring goes than from "Ready" state to "Active" state and shows the name of the LMS login account within the monitoring. So if screen proctoring generally works for you with an Exam without LMS but not for Olat now, I expect this is because of that you're using OpenOlat that do not have full SEB Server integration yet as Olat (from UZH) has. If you would like to address full SEB Server support, you can either consider contacting the people on UZH that did the SEB Server integration for Olat or the people on OpenOlat to ask them to consider a full SEB Server integration. About the OAuth token table. This is just the way the Spring framework encodes user authentications on data layer level. Generally I recommend doing not manually change data in the database since we cannot guarantee data consistency then any more. Thank you again for your help and testing, and if you have further questions about SEB Server, or SEB Server LMS integration, please dont hesitate to ask here or via mail Best Regards |
Beta Was this translation helpful? Give feedback.
-
|
Hi Andreas, I kind of expected that outcome but now I know for sure and others have to decide how we advance from that point on. Thanks again for the great support! Kind regards, |
Beta Was this translation helpful? Give feedback.
Hi Stephan,
Thanks for the detailed information.
For me now, it is relatively clear that screen proctoring doesn't work with Olat because your Olat instance do not have full SEB Server integration support. As far as I know, only the Olat developed by UZH has full SEB Server integration yet. They tried to rely on standard API calls as best as possible, but not every feature was able to be implemented with the standard API but needed an extension. Namely, the SEB Restriction feature as well as the Login and Name Resolving feature. The second one is essential for screen proctoring, since only when SEB detects a LMS login, it sends the user identifier to SEB Server this will trigger name reso…