{"action":"opened","issue":{"url":"https://api.github.com/repos/Igalia/phpreport/issues/122","repository_url":"https://api.github.com/repos/Igalia/phpreport","labels_url":"https://api.github.com/repos/Igalia/phpreport/issues/122/labels{/name}","comments_url":"https://api.github.com/repos/Igalia/phpreport/issues/122/comments","events_url":"https://api.github.com/repos/Igalia/phpreport/issues/122/events","html_url":"https://github.com/Igalia/phpreport/issues/122","id":139535467,"number":122,"title":"Prevent modification of user data when using LDAP authentication","user":{"login":"jaragunde","id":2900877,"avatar_url":"https://avatars.githubusercontent.com/u/2900877?v=3","gravatar_id":"","url":"https://api.github.com/users/jaragunde","html_url":"https://github.com/jaragunde","followers_url":"https://api.github.com/users/jaragunde/followers","following_url":"https://api.github.com/users/jaragunde/following{/other_user}","gists_url":"https://api.github.com/users/jaragunde/gists{/gist_id}","starred_url":"https://api.github.com/users/jaragunde/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jaragunde/subscriptions","organizations_url":"https://api.github.com/users/jaragunde/orgs","repos_url":"https://api.github.com/users/jaragunde/repos","events_url":"https://api.github.com/users/jaragunde/events{/privacy}","received_events_url":"https://api.github.com/users/jaragunde/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/Igalia/phpreport/labels/AJAX_interface","name":"AJAX_interface","color":"FFFFFF"},{"url":"https://api.github.com/repos/Igalia/phpreport/labels/bug","name":"bug","color":"fc2929"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2016-03-09T10:21:46Z","updated_at":"2016-03-09T10:21:46Z","closed_at":null,"body":"[Trac import]\nReported by: jaragunde\nOriginal date: Monday, 15 November 2010 20:36\n\nCurrently if LDAP authentication is enabled, admin users still can double-click on a user in the user management screen, and try to modify some data, for example, their login name or user groups. The model pops an !UnsupportedOperationException, and the AJAX interface shows an error, but the changes in the login name are performed anyway. A user with a changed login name becomes inconsistent (doesn't exist in the LDAP and in DB at the same time) and isn't able to login again.\r\n\r\nThere are two problems here:\r\n   * The interface should prevent the modification of the following user data: login, password and groups.\r\n   * The model layer shouldn't be able to do part of the changes (the login name) and throw an exception at the same time."}}