[
https://issues.apache.org/jira/browse/GUACAMOLE-1137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17159455#comment-17159455
]
Mike Jumper commented on GUACAMOLE-1137:
----------------------------------------
{quote}
Whithout @ the request works
{quote}
Sure. "[email protected]" and "test" are both perfectly valid usernames for
different users.
{quote}
The sql user has all permmissions to do changes. I already checked. Otherwiese
also the admin would have a problem to update. It was also my first idea.
{quote}
No, the fact that the administrator has the correct privileges does not imply
that the non-administrative user has the correct privileges.
{quote}
Is a @ in the non-admin-username the “class
org.apache.guacamole.auth.jdbc.user.UserDirectory” within the variable
"directory" is not set prober.
{quote}
I'm not sure what you're saying here, but to clarify: the formatting of a
username has absolutely nothing to do with permissions within Guacamole. It is
purely an arbitrary string that identifies a user. If you are seeing a 404
response for a REST API request related to a particular user, this means either
of the following is true:
* The user does not exist.
* The user exists but the current user does not have "READ" permission on that
user.
It is conceivable that a bug could cause all users containing "@" within their
usernames to be inaccessible, but you have already established that this is not
the case through testing an administrator having the same formatting. The only
possibility here is a problem with permissions.
Am I correct in my guess that you manually created this user via SQL? What
specific permissions did you insert when that user was created? Perhaps you can
share the relevant SQL, or query the permissions granted to that user and post
the results here?
> User can not change the own password
> ------------------------------------
>
> Key: GUACAMOLE-1137
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1137
> Project: Guacamole
> Issue Type: Bug
> Reporter: Stefan
> Priority: Minor
>
> We noticed some strange behavior when the user wants to change its password.
> When there is a "@” sign in the username and he not an administrator the
> password change is not possible. (tomcat-server response with 404).
> Hs a admin an "@" in the username is no problem.
> Also, when the non-admin-user has no "@" in the username the password change
> is working.
> We started search but up to now we have no idea where the issue happens…
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
