You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@guacamole.apache.org by "Nick Couchman (JIRA)" <ji...@apache.org> on 2018/02/04 15:00:00 UTC

[jira] [Updated] (GUACAMOLE-305) Implement Active Session and History Tracking in LDAP Module

     [ https://issues.apache.org/jira/browse/GUACAMOLE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Couchman updated GUACAMOLE-305:
------------------------------------
    Affects Version/s:     (was: 0.9.13-incubating)
                           (was: 0.9.12-incubating)

> Implement Active Session and History Tracking in LDAP Module
> ------------------------------------------------------------
>
>                 Key: GUACAMOLE-305
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-305
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-auth-ldap
>            Reporter: Kurt Kellner
>            Priority: Minor
>
> If users and connections are defined within LDAP the negative impact is that  session are not logged in "History" records or show any "Active Sessions" in the Guacamole settings area. 
> I assume this because of referential integrity within MySQL (e.g., if there is no user or connection record within MySQL, the history table can't hold the record).   As LDAP becomes more popular as a store of users/connections need to figure out a way to enable the Active sessions and History functionality.   Maybe the data should just be inserted with username and connection name.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)