[
https://issues.apache.org/jira/browse/KNOX-749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15765561#comment-15765561
]
Larry McCay commented on KNOX-749:
----------------------------------
Turns out this is most likely unnecessary.
The CSRF protection by default does not get enforced for GETs which is all the
browser will do for UI pages. They can be co-located in the same topologies
after all.
We can figure out whether we want to add it to the existing admin.xml file or
not.
Seems like it would be simplest to be available in admin.xml but it may get
overwritten during upgrades. In which case, admins will have to know to go add
it to the topology or deploy a new one like manager.xml.
Also, if HTTP Basic is not sufficient we may want to change the authentication
provider to use KnoxSSO admins will need to know not to break the admin users
like ranger that will not use KnoxSSO from the server side.
Personally, I think that adding it to admin.xml will allow us to manage it
within Ambari since it is aware of admin.xml and then access the UI to add a
new one for use with KnoxSSO - since Ambari doesn't know about arbitrary
topologies. That holds together for me.
> Simple Admin UI
> ---------------
>
> Key: KNOX-749
> URL: https://issues.apache.org/jira/browse/KNOX-749
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Larry McCay
> Assignee: Sumit Gupta
> Fix For: 0.11.0
>
> Attachments: knox-admin-ui-001.patch
>
>
> We need to a simple UI for management/admin insights based on the Knox Admin
> API.
> We can start with a read-only iteration and extend it in a future release.
> [~zacblanco] has expressed interest in this effort on the dev list and
> possibly other JIRAs.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
