[
https://issues.apache.org/jira/browse/GUACAMOLE-1222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17238996#comment-17238996
]
Mike Jumper commented on GUACAMOLE-1222:
----------------------------------------
I suspect that this is happening because the username part of the history
search is being done via a join on the user/entity table:
https://github.com/apache/guacamole-client/blob/70315d6dcbe02c60bd31e79dae2e4f1d2bb04a71/extensions/guacamole-auth-jdbc/modules/guacamole-auth-jdbc-mysql/src/main/resources/org/apache/guacamole/auth/jdbc/connection/ConnectionRecordMapper.xml#L120-L124
The username is duplicated within the history records in text form so that
records continue to exist even if a user is deleted (or a user is not defined
in the database at all). The query likely needs to be modified to use _that_
column instead, with only the non-administrator search relying on the join.
The same probably goes for connection names. For administrative users, the
search should use the connection name stored directly in the record, rather
than relying on a join against connection table entries that may no longer
exist.
> search field in "History" does not work as expected
> ---------------------------------------------------
>
> Key: GUACAMOLE-1222
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1222
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole
> Affects Versions: 1.2.0
> Reporter: Jason Keltz
> Priority: Major
>
> The "Search" field in "Active Sessions" works perfectly for all usernames and
> hostnames. However, the search field in "History" does not work properly for
> users. It works for connections, but I frequently have users literally listed
> right on the display, and when I enter a username, I get back 0 matches.
> (sent to list on oct. 21 with no replies and hence posting here as a
> potential bug)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
