You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2017/06/27 09:35:00 UTC
[jira] [Commented] (QPID-7838) Make AMQP Management Node respect
secure attributes and secure operations
[ https://issues.apache.org/jira/browse/QPID-7838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16064553#comment-16064553 ]
ASF subversion and git services commented on QPID-7838:
-------------------------------------------------------
Commit 3d0428385349a01c1a8f231a7e1407ec4069b32b in qpid-broker-j's branch refs/heads/master from [~k-wall]
[ https://git-wip-us.apache.org/repos/asf?p=qpid-broker-j.git;h=3d04283 ]
QPID-7838: [AMQP Management] Respect semantics of model secure attributes and operations
Also:
* fixed defect that prevented the invocation of operations that were declared of a non-category class.
* managed operations now return a response message payload appropiate to their return type (rather than serialised java object).
* pushed up HttpPort#allowConfidentialOperationsOnInsecureChannels Port as it also applies to AmqpPorts too.
> Make AMQP Management Node respect secure attributes and secure operations
> -------------------------------------------------------------------------
>
> Key: QPID-7838
> URL: https://issues.apache.org/jira/browse/QPID-7838
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Keith Wall
> Fix For: qpid-java-broker-7.0.0
>
>
> The AMQP Management Node currently enforces neither operations that require a secure channel nor attributes that are marked as secure. It should.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org