You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@guacamole.apache.org by "Cameron Price (JIRA)" <ji...@apache.org> on 2017/10/06 17:04:00 UTC

[jira] [Closed] (GUACAMOLE-404) Users can log in via ldap - active directory, with case insenstive usernames, but guac won't recognize them

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

Cameron Price closed GUACAMOLE-404.
-----------------------------------

> Users can log in via ldap - active directory, with case insenstive usernames, but guac won't recognize them
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: GUACAMOLE-404
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-404
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-auth-jdbc-postgresql, guacamole-auth-ldap
>         Environment: docker
>            Reporter: Cameron Price
>
> Hi there, 
> We have ldap auth working for us via active directory. We have issues with case senstivity around logins. For example most users have no idea if their username is
> User.Name
> or USER.NAME or whatever. - active directory doesnt care about case, and neither does ldap authentication.  
> But when they log in to guac and do not match the case of their login exactly, guac allows them to log in, but they just don't have any machines to connect to.
> Wondering if it could be made to either fail the logins if it doesn't match correct case, or ignore case when matching the username in the local guac db.
> Thanks



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)