[
https://issues.apache.org/jira/browse/GUACAMOLE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16023109#comment-16023109
]
Nick Couchman commented on GUACAMOLE-284:
-----------------------------------------
Cool. So simple solution to this seems to be to check for disabled/expired
accounts in the methods that return configurations for the accounts, and just
return empty or null if that's the case. Is that the route to go, or is there
a more proper/elegant way you'd go about it?
> When using ldap with MySQL backend "Account Restrictions" doesn't work
> ----------------------------------------------------------------------
>
> Key: GUACAMOLE-284
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-284
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-jdbc-mysql, guacamole-auth-ldap,
> guacamole-client
> Affects Versions: 0.9.12-incubating
> Reporter: Mark van den Boogaard
>
> When using LDAP authentication and a MySQL backend the options under "Account
> Restrictions" are not working.
> When we set the option "Disabled" or "Enable/Disable account after" this has
> no effect.
> For us the users who managing Guacamole (users and connections) do not have
> access to LDAP to enable/disable accounts. So it would be nice to do have
> these options working when using LDAP authentication with MySQL
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
