[
https://issues.apache.org/jira/browse/GUACAMOLE-1081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17116732#comment-17116732
]
Jason Keltz edited comment on GUACAMOLE-1081 at 5/26/20, 1:22 PM:
------------------------------------------------------------------
I tried to integrate this into my production 1.1.0 early this morning, but no
success.
I downloaded guacamole-client zip, applied the patch, ran mvn package and
everything was fine. I replaced the war file with the one I'd just compiled.
I made the following changes to a connection:
* username: ${GUAC_USERNAME:lower}
* SFTP username same
* and the reference to ${GUAC_USERNAME} in sftp file browser root directory to
same
I logged in with all CAPS, and was still unsuccessful in opening that
connection.
Just in case, I tried to replace the ldap module as well, but that didn't
change anything (I didn't think it would).
I also tried to disable SFTP altogether. This time, it failed, but XRDP popped
up a box with username actually being: ${GUAC_USERNAME:lower}
Interestingly enough, in the history, the username recorded *was* in fact the
lowercase version of the username.
While this system (when fixed) will work perfectly for my case, it's important
to note that it would not work for a case where systems actually do support
mixed case usernames and the admin can't use :lower/:upper. In this case, they
would have to stick with the default option, and accept that logins using
different case would fail.
was (Author: kangaroo22):
I tried to integrate this into my production 1.1.0 early this morning, but no
success.
I downloaded guacamole-client zip, applied the patch, ran mvn package and
everything was fine. I replaced the war file with the one I'd just compiled.
I made the following changes to a connection:
* username: ${GUAC_USERNAME:lower}
* SFTP username same
* and the reference to ${GUAC_USERNAME} in sftp file browser root directory to
same
I logged in with all CAPS, and was still unsuccessful in opening that
connection.
Just in case, I tried to replace the ldap module as well, but that didn't
change anything (I didn't think it would).
I also tried to disable SFTP altogether. This time, it failed, but XRDP popped
up a box with username actually being: ${GUAC_USERNAME:lower}
While this system (when fixed) will work perfectly for my case, it's important
to note that it would not work for a case where systems actually do support
mixed case usernames and the admin can't use :lower/:upper. In this case, they
would have to stick with the default option, and accept that logins using
different case would fail.
> option to convert usernames to all lowercase
> --------------------------------------------
>
> Key: GUACAMOLE-1081
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1081
> Project: Guacamole
> Issue Type: New Feature
> Components: Documentation, guacamole-ext
> Reporter: Jason Keltz
> Assignee: Nick Couchman
> Priority: Minor
> Fix For: 1.3.0
>
>
> When the user logs into Guac with parts of their username in uppercase, the
> login to Guac is successful, but then subsequent login to Linux systems fails
> because the username is case sensitive. It would be useful to have an option
> in Guacamole to convert usernames to lowercase or uppercase before passing on
> to the systems.
> One possible suggestion from Nick on the mailing list was something like this:
>
> ${GUAC_USERNAME} - Pass through as entered
> ${GUAC_USERNAME:lower} - Convert string to lower-case
> ${GUAC_USERNAME:upper} - Convert string to upper-case
>
> This would work very well.
> I would be likewise happy with a solution that let me set a default somewhere
> (in my case, all lowercase).
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
