Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 6447F200CD8 for ; Wed, 2 Aug 2017 15:03:04 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 62997168E41; Wed, 2 Aug 2017 13:03:04 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id A7E31168E3F for ; Wed, 2 Aug 2017 15:03:03 +0200 (CEST) Received: (qmail 83772 invoked by uid 500); 2 Aug 2017 13:03:02 -0000 Mailing-List: contact commits-help@guacamole.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@guacamole.incubator.apache.org Delivered-To: mailing list commits@guacamole.incubator.apache.org Received: (qmail 83763 invoked by uid 99); 2 Aug 2017 13:03:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 02 Aug 2017 13:03:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 77BCE18041D for ; Wed, 2 Aug 2017 13:03:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id QB_hyB7vu0Q9 for ; Wed, 2 Aug 2017 13:03:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 6A6B25F5C4 for ; Wed, 2 Aug 2017 13:03:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id B29FFE08B4 for ; Wed, 2 Aug 2017 13:03:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 5E0BC2464D for ; Wed, 2 Aug 2017 13:03:00 +0000 (UTC) Date: Wed, 2 Aug 2017 13:03:00 +0000 (UTC) From: "Nick Couchman (JIRA)" To: commits@guacamole.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (GUACAMOLE-305) Use of LDAP for users/connection should not prevent Active Sessions and History MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 02 Aug 2017 13:03:04 -0000 [ https://issues.apache.org/jira/browse/GUACAMOLE-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16110848#comment-16110848 ] Nick Couchman commented on GUACAMOLE-305: ----------------------------------------- Currently Active Sessions are stored completely in-memory - there is a history table for historical connections, but it is only populated after the connection completes. There are some discussions about changing this for the purposes of HA, but no direction has been decided upon, yet. > 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 > 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 (v6.4.14#64029)