[jira] [Commented] (GUACAMOLE-1742) Implement Active and Historical Connection Tracking in JSON Module

["Nick Couchman (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GUACAMOLE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692807#comment-17692807 ] 

Nick Couchman commented on GUACAMOLE-1742:
------------------------------------------

[~phreakocious]: This isn't really a "visibility" issue so much as it's the fact that the JSON module does not implement any of the active or historical connection tracking bits that the database module has. The JDBC modules are actually the only ones that currently implement this functionality - LDAP, JSON, and Ad-Hoc do not track any of these.

If you want this information available you'd need to implement active connection tracking in the JSON module. The good news is that recent changes to the JDBC module allow it to store information like historical records for other modules, so at least part of that is done.

> Implement Active and Historical Connection Tracking in JSON Module
> ------------------------------------------------------------------
>
>                 Key: GUACAMOLE-1742
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-1742
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole-auth-json
>            Reporter: phreakocious
>            Priority: Minor
>
> There are a few components to this, which I suspect have the same root cause.
> When using the JSON authentication in combination with a database, active connections are not visible in the web app for administrators and history for them is not logged.  They also don't appear in the activeConnections API endpoint and no datasource named 'json' is present.  This is not ideal for dashboards monitoring active connections.
>  
> If someone familiar with the work needed to address any of those would like to give some direction, I'd be happy to look at making the necessary updates. (Assuming it's possible for these to coexist in this way)



--
This message was sent by Atlassian Jira
(v8.20.10#820010)