[jira] [Commented] (GUACAMOLE-75) Cloning a user results in a blank error dialog

["Michael Jumper (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/GUACAMOLE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15419164#comment-15419164 ] 

Michael Jumper commented on GUACAMOLE-75:
-----------------------------------------

This is due to the implicit permissions granted upon user creation (self read) conflicting with the permissions being inserted due to inheritance from the cloned user (who also has self read).

The problem will not occur with MySQL, as the {{INSERT}} has been written to ignore duplicate keys for permissions. The PostgreSQL query does not do this, however.

> Cloning a user results in a blank error dialog
> ----------------------------------------------
>
>                 Key: GUACAMOLE-75
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-75
>             Project: Guacamole
>          Issue Type: Bug
>          Components: guacamole-auth-jdbc
>            Reporter: Michael Jumper
>            Assignee: Michael Jumper
>            Priority: Blocker
>             Fix For: 0.9.10-incubating
>
>
> When attempting to create a user using the "Clone" button, clicking "Save" universally results in a blank error dialog. The underlying error is a unique key violation due to duplicate permission for the user to read themselves:
> {quote}
> {code:none}
> ...
> Caused by: org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "guacamole_user_permission_pkey"
>   Detail: Key (user_id, affected_user_id, permission)=(8, 8, READ) already exists.
> ...
> {code}
> {quote}
> The code handling saving of permissions within the JDBC auth *should* be saving only unique permissions ... but apparently is not.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)