[
https://issues.apache.org/jira/browse/QPID-7594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7594:
-----------------------------
Fix Version/s: (was: qpid-java-broker-7.0.0)
qpid-java-broker-7.1.0
> [Java Broker] Refactor Web Management Console to support virtual host
> centric UI
> ---------------------------------------------------------------------------------
>
> Key: QPID-7594
> URL: https://issues.apache.org/jira/browse/QPID-7594
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Reporter: Alex Rudyy
> Fix For: qpid-java-broker-7.1.0
>
>
> Virtual host centric REST interfaces have been added as part of QPID-7563.
> The Web Management Console needs to be changed to support virtual host
> centric REST interfaces and provide a Virtualhost centric UI to the end user.
> As part of QPID-7563 the existing servlets( REST, apidocs, Structure,
> MetaData, Query and QueueReports) have been updated so, that if the request
> is determined to have come through on a URL which is aliases to a specific
> vhost, then the results from the servlet will be specific to the vhost, and
> paths will reflect a virtual host root. The Web Management Console at the
> moment does not respect the virtual host root. The following changes are
> required to fully support virtual host centric view:
> * VH aliases UI should be available for the HTTP port. User should be able to
> add/remove aliases for HTTP port
> * On user authentication, the Console invokes Broker operations getUser,
> getGroups to get the authenticated user and groups. It seems corresponding
> operations need to be added to VH and the Console would need to call VH to
> retrieve user and group information. Management#getAuthenticatedUserAndGroups
> should respect VH root. At the moment "broker" root is hard-coded in the
> method.
> * Console uses Broker userpreferences to get the timezone, tabs, etc. It
> seems that Console should be getting userpreferences from VH in VH centric
> view
> * Console tries to open a Broker tab by default. In VH centric view the VH
> tab should be opened instead.
> * On clicking on root item in a navigation tree a VH tab should be opened. At
> the moment, Broker tab is opened.
> * Queue tab should not be calling querybroker to get the queue depth.It
> should call VH query API instead.
> * Saving tab in preference should work against VH in VH centric view
> * Dashboard UI in VH centric view do not need to cal broker preferences.
> Dashboard creation dialog displays the correct VH but somehow it is not
> selected. It seems that this dialog can be completely omitted in VH centric
> view.
> * Query UI should be executed against VH query rest API. The dialog to create
> query displays the correct VH selected but somehow it is not selected and
> broker API is called. That needs to be fixed. Potentially, the widget for
> selection of association of query can be disabled or hidden. The same is for
> query cloning dialog
> * Preferences dialog calls broker userpreferences. In VH centric view VH
> userpreferences should be used
> At the moment, it is unclear how to display all available VH for the user
> (in order to provide a convenient way to switch between VHs). Even if user
> have access to multiple VHs, the DNS sub-domain and VH alias for http port
> might not be configured. Potentially, http port aliases can be used to
> assume that sub-domain is configured. I am not sure whether we really need a
> UI for switching between multiple VHs.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
