Our students and staff are being kicked out of activities after a short amount of time. We have staff members that need multiple tabs open, and used to be able to go between Buzz tabs for about an hour and now they are being logged out within minutes. Please let us know what we can do, and if we can open a ticket as well. Thank you!
This can occur if the domain they are authenticated to is using SSO authentication and the provider has ended their session in the other browser tab.
Could you please provide an enrollment ID of a user experiencing this as well as two activity IDs they had open when their session ended? Using these, I will be able to investigate this further.
I am happy to provide additional insight! Those two domains have an idle timeout of 20 minutes and the two activities are using LTI tools. Because the LTI is loading their content within an iframe, Buzz doesn't update the idle time within it unless there is action such as the user moves their cursor outside of the iframe container inside Buzz. The simplest solution would be to increase the domain's idle timeout to a higher value that accommodates the time users need to work through LTI activities.
The domains are also using SSO for authentication. So, another possible option for troubleshooting is to confirm timeouts don't occur before 20 minutes by authenticating directly to Buzz and not through SSO. If the timeout behavior doesn't manifest under 20 minutes, then the school with need to work with their SSO provider and possibly increase their session timeout limits.
Buzz should be pushing a dialogue message for users who encounter an idle timeout. Are the users encountering a message in Buzz when they timeout? If so, could you provide a screenshot of what they are seeing?
Comments (3)
Good morning Giovani,
This can occur if the domain they are authenticated to is using SSO authentication and the provider has ended their session in the other browser tab.
Could you please provide an enrollment ID of a user experiencing this as well as two activity IDs they had open when their session ended? Using these, I will be able to investigate this further.
Hello Allison,
Here is that information for you.
Hello everyone!
I am happy to provide additional insight! Those two domains have an idle timeout of 20 minutes and the two activities are using LTI tools. Because the LTI is loading their content within an iframe, Buzz doesn't update the idle time within it unless there is action such as the user moves their cursor outside of the iframe container inside Buzz. The simplest solution would be to increase the domain's idle timeout to a higher value that accommodates the time users need to work through LTI activities.
The domains are also using SSO for authentication. So, another possible option for troubleshooting is to confirm timeouts don't occur before 20 minutes by authenticating directly to Buzz and not through SSO. If the timeout behavior doesn't manifest under 20 minutes, then the school with need to work with their SSO provider and possibly increase their session timeout limits.
Buzz should be pushing a dialogue message for users who encounter an idle timeout. Are the users encountering a message in Buzz when they timeout? If so, could you provide a screenshot of what they are seeing?