[
https://issues.apache.org/jira/browse/GUACAMOLE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16016812#comment-16016812
]
Michael Jumper commented on GUACAMOLE-305:
------------------------------------------
The reason connections within LDAP do not show up within Active Sessions and
History is that the LDAP auth doesn't currently implement those features. The
only authentication backend which does thus far is the database auth.
Within Guacamole's extension architecture, it is up to each extension to
provide its own connection tracking semantics. That's not to say this isn't
doable. I'd say that some of the internals of the database auth should be moved
into a common library which the other auth backends could share, rather than
reimplement.
> Use of LDAP for users/connection should not prevent Active Sessions and
> History
> -------------------------------------------------------------------------------
>
> Key: GUACAMOLE-305
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-305
> Project: Guacamole
> Issue Type: Improvement
> Affects Versions: 0.9.12-incubating
> Reporter: Kurt Kellner
>
> 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
(v6.3.15#6346)
