[
https://issues.apache.org/jira/browse/GUACAMOLE-1062?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jerome Charaoui updated GUACAMOLE-1062:
---------------------------------------
Description:
We'd love to be able to specify, for a given connection or connection group, an
hourly timeframe (eg. 2PM to 4PM) during which the connection may be used. A
number of minutes before the end of the time slot, the user would receive a
message of imminent disconnection. If the user stays connected, then at the end
of the time slot the user is simply disconnected automatically.
Our specific use case is to provide remote access to student labs during the
present COVID-19 pandemic. These labs are to be used in the context of remote
teaching. The challenge is that more than one group of teacher/students are to
share the same lab and set of machines.
We need to be able to manage the timeslots for which each users are able to
access the machines, otherwise we worry that at the beginning of any given
remote class, students from other groups may already be occupying a number of
machines. We could do this by creating multiple connexion groups with different
schedules, using the same hostnames/machines, and assign access to those
connections accordingly.
There's already the ability to limit access per user account, but this isn't
ideal as it would prevent users from using any other connection (eg. to
free-access labs without a class schedule) outside those limits.
was:
We'd love to be able to specify, for a given connection or connection group, an
hourly timeframe (eg. 2PM to 4PM) during which the connection may be used. A
number of minutes before the end of the time slot, the user would receive a
message of imminent disconnection. If the user stays connected, then at the end
of the time slot the user is simply disconnected automatically.
Our specific use case is to provide remote access to student labs during the
present COVID-19 pandemic. These labs are to be used in the context of remote
teaching. The challenge is that more than one group of teacher/students are to
share the same lab and set of machines.
We need to be able to manage the timeslots for which each users are able to
access the machines, otherwise we worry that at the beginning of any given
remote class, students from other groups may already be occupying a number of
machines. We could do this by creating multiple connexion groups with different
schedules, using the same hostnames/machines, and assign access to those
connections accordingly.
There's already the ability to limit access per user account, but this isn't
ideal as it would prevent users from using any other connection outside those
limits.
> Connexion availability schedule
> -------------------------------
>
> Key: GUACAMOLE-1062
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1062
> Project: Guacamole
> Issue Type: New Feature
> Components: guacamole
> Affects Versions: 1.1.0
> Reporter: Jerome Charaoui
> Priority: Minor
>
> We'd love to be able to specify, for a given connection or connection group,
> an hourly timeframe (eg. 2PM to 4PM) during which the connection may be used.
> A number of minutes before the end of the time slot, the user would receive a
> message of imminent disconnection. If the user stays connected, then at the
> end of the time slot the user is simply disconnected automatically.
> Our specific use case is to provide remote access to student labs during the
> present COVID-19 pandemic. These labs are to be used in the context of remote
> teaching. The challenge is that more than one group of teacher/students are
> to share the same lab and set of machines.
> We need to be able to manage the timeslots for which each users are able to
> access the machines, otherwise we worry that at the beginning of any given
> remote class, students from other groups may already be occupying a number of
> machines. We could do this by creating multiple connexion groups with
> different schedules, using the same hostnames/machines, and assign access to
> those connections accordingly.
> There's already the ability to limit access per user account, but this isn't
> ideal as it would prevent users from using any other connection (eg. to
> free-access labs without a class schedule) outside those limits.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
