[
https://issues.apache.org/jira/browse/QPID-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17680991#comment-17680991
]
Daniil Kirilyuk commented on QPID-8619:
---------------------------------------
Hi,
Could you please provide an excerpt containing an example AccessControlProvider
configuration from your config.json file? Which endpoints do you currently use
to retrieve ACL information?
Kind regards,
Daniil
> Easier ACL interface for REST management (JSON output?)
> -------------------------------------------------------
>
> Key: QPID-8619
> URL: https://issues.apache.org/jira/browse/QPID-8619
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Affects Versions: qpid-java-broker-9.0.0
> Reporter: Kyrre
> Priority: Minor
>
> We use the management interface over HTTPS to create queues and exchanges, as
> well as managing ACLs to give and remove access to said queues and exchanges.
> We have lots of extra code to parse ACLs from the management interface, which
> is brittle and prone to braking. The ACLs are stored in the config.json as
> JSON, and then transformed to a bespoke format returned to the client, which
> then has to parse this format for manipulation. Would it not be much easier
> to just return the JSON, which is a lot easier to parse?
> If there's code/clients that require the bespoke format, maybe return JSON on
> a parameter/request header?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
