[ https://issues.apache.org/jira/browse/QPID-8619?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681013#comment-17681013 ]
Daniil Kirilyuk commented on QPID-8619: --------------------------------------- Thank you for clarification. Following endpoint can be used: {noformat} GET /api/latest/virtualhostaccesscontrolprovider/default/default/default{noformat} producing the output {code:java} { "id" : "a7ca4d04-9c99-48f5-bdc3-9557ca2cfdb9", "name" : "default", "type" : "RuleBased", "desiredState" : "ACTIVE", "state" : "ACTIVE", "durable" : true, "lifetimePolicy" : "PERMANENT", "defaultResult" : "DENIED", "lastOpenedTime" : 1674743093329, "priority" : 10, "rules" : [ { "objectType" : "EXCHANGE", "attributes" : { "ROUTING_KEY" : "onramp", "NAME" : "" }, "outcome" : "ALLOW_LOG", "identity" : "service-providers", "operation" : "PUBLISH" }, { "objectType" : "VIRTUALHOST", "attributes" : { "NAME" : "localhost" }, "outcome" : "ALLOW_LOG", "identity" : "service-providers", "operation" : "ACCESS" }, { "objectType" : "VIRTUALHOST", "attributes" : { "NAME" : "localhost" }, "outcome" : "ALLOW_LOG", "identity" : "clients-private-channels", "operation" : "ACCESS" }, { "objectType" : "QUEUE", "attributes" : { "NAME" : "bi-queue" }, "outcome" : "ALLOW_LOG", "identity" : "ALL", "operation" : "CONSUME" }, { "objectType" : "ALL", "attributes" : { }, "outcome" : "ALLOW_LOG", "identity" : "admin", "operation" : "ALL" } ], "createdTime" : 1674743091325 } {code} > 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