You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@guacamole.apache.org by "Michael Jumper (JIRA)" <ji...@apache.org> on 2017/06/07 03:41:18 UTC

[jira] [Resolved] (GUACAMOLE-284) Database "Account Restrictions" not applied when using LDAP

     [ https://issues.apache.org/jira/browse/GUACAMOLE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Jumper resolved GUACAMOLE-284.
--------------------------------------
       Resolution: Fixed
    Fix Version/s: 0.9.14-incubating

> 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
>             Fix For: 0.9.14-incubating
>
>
> 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)