[
https://issues.apache.org/jira/browse/GUACAMOLE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16036345#comment-16036345
]
Michael Jumper commented on GUACAMOLE-284:
------------------------------------------
More or less, yes.
I'm going to try moving those checks around, such that they are taken into
account when the "mysql-user-required" or "postgresql-user-required" options
are enabled.
> Database "Account Restrictions" not applied when using LDAP
> -----------------------------------------------------------
>
> Key: GUACAMOLE-284
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-284
> Project: Guacamole
> Issue Type: Bug
> Components: guacamole-auth-jdbc, guacamole-auth-ldap
> Affects Versions: 0.9.11-incubating, 0.9.12-incubating, 0.9.13-incubating
> Reporter: Mark van den Boogaard
> Assignee: Michael Jumper
> Priority: Minor
>
> When using LDAP authentication and a database 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 a database.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
