[ 
https://issues.apache.org/jira/browse/QPID-8371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Alex Rudyy updated QPID-8371:
-----------------------------
    Fix Version/s: qpid-java-broker-8.0.0

> [Broker-J][WMC] The error messages are not communicated back to user of web 
> management console on attempt to invoke operation without sufficient 
> permissions
> ------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: QPID-8371
>                 URL: https://issues.apache.org/jira/browse/QPID-8371
>             Project: Qpid
>          Issue Type: Bug
>          Components: Broker-J
>    Affects Versions: qpid-java-6.1, qpid-java-6.1.1, qpid-java-6.1.2, 
> qpid-java-6.1.3, qpid-java-6.1.4, qpid-java-broker-7.0.0, qpid-java-6.1.5, 
> qpid-java-broker-7.0.1, qpid-java-6.1.7, qpid-java-broker-7.1.0, 
> qpid-java-broker-7.0.4, qpid-java-broker-7.0.5, qpid-java-broker-7.0.6, 
> qpid-java-broker-7.0.7, qpid-java-broker-7.1.1, qpid-java-broker-7.1.2, 
> qpid-java-broker-7.0.8, qpid-java-broker-7.1.3, qpid-java-broker-7.1.4
>            Reporter: Alex Rudyy
>            Priority: Major
>             Fix For: qpid-java-broker-8.0.0, qpid-java-broker-7.1.5
>
>
> When a user without a permission to invoke queue operations tries to get 
> messages from the queue tab, the 403 response is returned by the broker with 
> an error message indicating about absence of required permission.  The web 
> management console does not display anything to the user. It simply acts as 
> nothing happens. As result, the end-user cannot understand what is going on 
> without looking into debug console. The UI should notify the user about 
> absence of permission by displaying a pertinent message.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to