[
https://issues.apache.org/jira/browse/GUACAMOLE-404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16194829#comment-16194829
]
Michael Jumper commented on GUACAMOLE-404:
------------------------------------------
Guacamole is case-sensitive when it comes to usernames, which determine
identity. If you are combining multiple authentication systems, only one of
which uses case-insensitive comparisons for usernames, things will not work as
expected.
{quote}
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.
{quote}
You can require the existence of a PostgreSQL user by setting the
{{postgresql-user-required}} property to {{true}} within your
guacamole.properties:
http://guacamole.incubator.apache.org/doc/gug/jdbc-auth.html#jdbc-auth-restrict
> 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)
