An attempt to remove role mapping of currently authenticated user leads to an error. Even though this might be in fact a feature, but in such case user should be informed about this fact in other way than standard error. At least the error message should contain the explanation why the removal failed.
Harald Pehl <hpehl> updated the status of jira HAL-282 to Resolved
Harald Pehl <hpehl> made a comment on jira HAL-282 Fixed by HAL-281. The error message reads now "You don't have the permissions to access this resource!"
This is the very same case as BZ1016546. The problem here might be the fact that this error message is shared among all unauthorized operations, thus it might be a bit confusing in some cases. Returning back to assigned, however I've changed the severity to low.
In agreement with Catherine we've decided that UX issues will be tracked separately.
Issue moved under the UX component. Also moved to 6.4 as this issue is still valid for 6.3. Use ack flags to decide whether we want to go through with it or not.
Can we update the description of the BZ. Does current user mean any user that's logged into the console currently, or does it refer to a user that's trying to modify his own role assignments? Ideally, we would present an error message that is specific to the task that a user is trying to perform. So in this case we would mention that a 'role assignments could not be changed be because you don't have access to resource X'.
User that's trying to modify his own role assignments.
Harald Pehl <hpehl> updated the status of jira HAL-292 to Resolved
This particular issue is fixed for EAP 6.4.0.DR3 but there are other related issues which I will report tomorrow.