[jira] [Updated] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lei Yao updated AMBARI-24118: - Fix Version/s: 3.0.0 (was: 2.9.0) > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 3.0.0 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhiguo Wu updated AMBARI-24118: --- Fix Version/s: 2.9.0 (was: 2.8.0) > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 2.9.0 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: issues-unsubscr...@ambari.apache.org For additional commands, e-mail: issues-h...@ambari.apache.org
[jira] [Updated] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Olivér Szabó updated AMBARI-24118: -- Fix Version/s: (was: 2.7.3) 2.8.0 > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 2.8.0 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24118: --- Fix Version/s: (was: 2.7.2) 2.7.3 > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 2.7.3 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jayush Luniya updated AMBARI-24118: --- Fix Version/s: (was: 2.7.1) 2.7.2 > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 2.7.2 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ishan Bhatt updated AMBARI-24118: - Fix Version/s: (was: 2.7.0) 2.7.1 > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 2.7.1 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry McCay updated AMBARI-24118: - Status: Patch Available (was: Open) AMBARI-24118-001.patch includes the minor adjustments to the default configuration described in the Description above. > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (AMBARI-24118) Update KNOX Service Config to Better Integrate the Knox Admin UI
[ https://issues.apache.org/jira/browse/AMBARI-24118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Larry McCay updated AMBARI-24118: - Attachment: AMBARI-24118-001.patch > Update KNOX Service Config to Better Integrate the Knox Admin UI > > > Key: AMBARI-24118 > URL: https://issues.apache.org/jira/browse/AMBARI-24118 > Project: Ambari > Issue Type: Bug > Components: ambari-sever >Reporter: Larry McCay >Assignee: Larry McCay >Priority: Major > Fix For: 2.7.0 > > Attachments: AMBARI-24118-001.patch > > > The manager.xml topology in Apache Knox hosts the endpoint for the Knox Admin > UI. In order to provide management of the configuration for access to the UI > we need to be able to manage the LDAP configuration for authentication, group > lookup and the ACLs for constraining access to admin users and groups. > We have taken a couple actions in Knox to facilitate this: > # Moved the authentication in manager.xml to leverage KnoxSSO as the > authentication mechanism. Will also buy us seamless SSO between Ambari and > Knox UIs. > # Made the group look up manageable from the gateway-site.xml and the > admin.xml and manager.xml topologies auto-redeploy on startup of the Knox > server to pick up gateway-site changes. > # Made the list of admin users and admin groups configurable in > gateway-site.xml > This patch will default the KNOX_ADMIN_USERS to "admin" and the > KNOX_ADMIN_GROUPS to "admin". These values will work with the Knox DEMO LDAP > server that can be used for demos and testing but will need to be adjusted to > the enterprise LDAP users/groups that require access to the Knox Admin UI. > The HadoopGroupProvider will assume the default configuration but when there > are no local OS accounts, the admin will be able to configure LDAP or other > group mapping mechanisms in gateway-site.xml via advanced params. > Lastly, the patch adds the admin group to the DEMO LDAP users.ldif file to > facilitate group lookup if needed. It will actually use no lookup by default > and will grant access to a user named "admin" only but can be configured to > use the admin group. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
