[
https://issues.apache.org/jira/browse/GUACAMOLE-1742?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17692830#comment-17692830
]
Nick Couchman commented on GUACAMOLE-1742:
------------------------------------------
[~phreakocious]: Yes, GUACAMOLE-1616 is the Jira issue that deals with that. It
is not present in the 1.5.0 release, but should be in the next one.
> 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)
