[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[
https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19038:
--
Resolution: Fixed
Status: Resolved (was: Patch Available)
Committed to trunk
{noformat}
commit f7fac03778fda337bc96ed49ed7507e1af118b7d
Author: Robert Levas
Date: Fri Jul 14 10:47:17 2017 -0400
{noformat}
> Support migration of LDAP users & groups to PAM
> ---
>
> Key: AMBARI-19038
> URL: https://issues.apache.org/jira/browse/AMBARI-19038
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vishal Ghugare
>Assignee: Robert Levas
> Fix For: 2.5.2
>
> Attachments: AMBARI-19038_branch-2.5_01.patch, AMBARI-19038.patch,
> AMBARI-19038_trunk_01.patch
>
>
> After PAM has been declared as the authentication mechanism for Ambari
> clients (for example, the Ambari Server web-based UI) where previously the
> mechanism was LDAP, a migration process is needed to converts the LDAP users
> and groups to PAM users and groups.
> This facility may be invoked using:
> {noformat}
> ambari-server migrate-ldap-pam
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[
https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19038:
--
Attachment: AMBARI-19038_trunk_01.patch
> Support migration of LDAP users & groups to PAM
> ---
>
> Key: AMBARI-19038
> URL: https://issues.apache.org/jira/browse/AMBARI-19038
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vishal Ghugare
>Assignee: Robert Levas
> Fix For: 2.5.2
>
> Attachments: AMBARI-19038_branch-2.5_01.patch, AMBARI-19038.patch,
> AMBARI-19038_trunk_01.patch
>
>
> After PAM has been declared as the authentication mechanism for Ambari
> clients (for example, the Ambari Server web-based UI) where previously the
> mechanism was LDAP, a migration process is needed to converts the LDAP users
> and groups to PAM users and groups.
> This facility may be invoked using:
> {noformat}
> ambari-server migrate-ldap-pam
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[
https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19038:
--
Issue Type: Task (was: Story)
> Support migration of LDAP users & groups to PAM
> ---
>
> Key: AMBARI-19038
> URL: https://issues.apache.org/jira/browse/AMBARI-19038
> Project: Ambari
> Issue Type: Task
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vishal Ghugare
>Assignee: Robert Levas
> Fix For: 2.5.2
>
> Attachments: AMBARI-19038_branch-2.5_01.patch, AMBARI-19038.patch
>
>
> After PAM has been declared as the authentication mechanism for Ambari
> clients (for example, the Ambari Server web-based UI) where previously the
> mechanism was LDAP, a migration process is needed to converts the LDAP users
> and groups to PAM users and groups.
> This facility may be invoked using:
> {noformat}
> ambari-server migrate-ldap-pam
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[
https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19038:
--
Status: Patch Available (was: In Progress)
> Support migration of LDAP users & groups to PAM
> ---
>
> Key: AMBARI-19038
> URL: https://issues.apache.org/jira/browse/AMBARI-19038
> Project: Ambari
> Issue Type: Story
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vishal Ghugare
>Assignee: Robert Levas
> Fix For: 2.5.2
>
> Attachments: AMBARI-19038_branch-2.5_01.patch, AMBARI-19038.patch
>
>
> After PAM has been declared as the authentication mechanism for Ambari
> clients (for example, the Ambari Server web-based UI) where previously the
> mechanism was LDAP, a migration process is needed to converts the LDAP users
> and groups to PAM users and groups.
> This facility may be invoked using:
> {noformat}
> ambari-server migrate-ldap-pam
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[
https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19038:
--
Attachment: AMBARI-19038_branch-2.5_01.patch
> Support migration of LDAP users & groups to PAM
> ---
>
> Key: AMBARI-19038
> URL: https://issues.apache.org/jira/browse/AMBARI-19038
> Project: Ambari
> Issue Type: Story
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vishal Ghugare
>Assignee: Robert Levas
> Fix For: 2.5.2
>
> Attachments: AMBARI-19038_branch-2.5_01.patch, AMBARI-19038.patch
>
>
> After PAM has been declared as the authentication mechanism for Ambari
> clients (for example, the Ambari Server web-based UI) where previously the
> mechanism was LDAP, a migration process is needed to converts the LDAP users
> and groups to PAM users and groups.
> This facility may be invoked using:
> {noformat}
> ambari-server migrate-ldap-pam
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[
https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Levas updated AMBARI-19038:
--
Description:
After PAM has been declared as the authentication mechanism for Ambari clients
(for example, the Ambari Server web-based UI) where previously the mechanism
was LDAP, a migration process is needed to converts the LDAP users and groups
to PAM users and groups.
This facility may be invoked using:
{noformat}
ambari-server migrate-ldap-pam
{noformat}
was:
Story to address migration of LDAP users & groups to PAM.
Note: LDAP usesids that collide with existing PAM userids in Ambari metastore
will not be migrated.
> Support migration of LDAP users & groups to PAM
> ---
>
> Key: AMBARI-19038
> URL: https://issues.apache.org/jira/browse/AMBARI-19038
> Project: Ambari
> Issue Type: Story
> Components: ambari-server
>Affects Versions: 2.5.2
>Reporter: Vishal Ghugare
>Assignee: Robert Levas
> Fix For: 2.5.2
>
> Attachments: AMBARI-19038.patch
>
>
> After PAM has been declared as the authentication mechanism for Ambari
> clients (for example, the Ambari Server web-based UI) where previously the
> mechanism was LDAP, a migration process is needed to converts the LDAP users
> and groups to PAM users and groups.
> This facility may be invoked using:
> {noformat}
> ambari-server migrate-ldap-pam
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[ https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-19038: -- Fix Version/s: (was: trunk) 2.5.2 > Support migration of LDAP users & groups to PAM > --- > > Key: AMBARI-19038 > URL: https://issues.apache.org/jira/browse/AMBARI-19038 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Ghugare >Assignee: Robert Levas > Fix For: 2.5.2 > > Attachments: AMBARI-19038.patch > > > Story to address migration of LDAP users & groups to PAM. > Note: LDAP usesids that collide with existing PAM userids in Ambari > metastore will not be migrated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[ https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-19038: -- Status: Open (was: Patch Available) Cancelling the out-dated patch for this. > Support migration of LDAP users & groups to PAM > --- > > Key: AMBARI-19038 > URL: https://issues.apache.org/jira/browse/AMBARI-19038 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Vishal Ghugare >Assignee: Robert Levas > Fix For: trunk > > Attachments: AMBARI-19038.patch > > > Story to address migration of LDAP users & groups to PAM. > Note: LDAP usesids that collide with existing PAM userids in Ambari > metastore will not be migrated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[ https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-19038: -- Affects Version/s: (was: trunk) > Support migration of LDAP users & groups to PAM > --- > > Key: AMBARI-19038 > URL: https://issues.apache.org/jira/browse/AMBARI-19038 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Ghugare >Assignee: Robert Levas > Fix For: 2.5.2 > > Attachments: AMBARI-19038.patch > > > Story to address migration of LDAP users & groups to PAM. > Note: LDAP usesids that collide with existing PAM userids in Ambari > metastore will not be migrated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[ https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Levas updated AMBARI-19038: -- Affects Version/s: (was: 2.5.0) 2.5.2 > Support migration of LDAP users & groups to PAM > --- > > Key: AMBARI-19038 > URL: https://issues.apache.org/jira/browse/AMBARI-19038 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: 2.5.2 >Reporter: Vishal Ghugare >Assignee: Robert Levas > Fix For: 2.5.2 > > Attachments: AMBARI-19038.patch > > > Story to address migration of LDAP users & groups to PAM. > Note: LDAP usesids that collide with existing PAM userids in Ambari > metastore will not be migrated. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[ https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Ghugare updated AMBARI-19038: Attachment: AMBARI-19038.patch > Support migration of LDAP users & groups to PAM > --- > > Key: AMBARI-19038 > URL: https://issues.apache.org/jira/browse/AMBARI-19038 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Vishal Ghugare >Assignee: Vishal Ghugare > Fix For: trunk > > Attachments: AMBARI-19038.patch > > > Story to address migration of LDAP users & groups to PAM. > Note: LDAP usesids that collide with existing PAM userids in Ambari > metastore will not be migrated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[ https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Ghugare updated AMBARI-19038: Fix Version/s: trunk Status: Patch Available (was: Open) > Support migration of LDAP users & groups to PAM > --- > > Key: AMBARI-19038 > URL: https://issues.apache.org/jira/browse/AMBARI-19038 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Vishal Ghugare >Assignee: Vishal Ghugare > Fix For: trunk > > Attachments: AMBARI-19038.patch > > > Story to address migration of LDAP users & groups to PAM. > Note: LDAP usesids that collide with existing PAM userids in Ambari > metastore will not be migrated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (AMBARI-19038) Support migration of LDAP users & groups to PAM
[ https://issues.apache.org/jira/browse/AMBARI-19038?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vishal Ghugare updated AMBARI-19038: Description: Story to address migration of LDAP users & groups to PAM. Note: LDAP usesids that collide with existing PAM userids in Ambari metastore will not be migrated. was: Story to address migration of LDAP users & groups to PAM. Note: All the users with conflicts ( two users with same username but one of LDAP & other of PAM type) will not be migrated from LDAP to PAM. > Support migration of LDAP users & groups to PAM > --- > > Key: AMBARI-19038 > URL: https://issues.apache.org/jira/browse/AMBARI-19038 > Project: Ambari > Issue Type: Story > Components: ambari-server >Affects Versions: trunk, 2.5.0 >Reporter: Vishal Ghugare >Assignee: Vishal Ghugare > > Story to address migration of LDAP users & groups to PAM. > Note: LDAP usesids that collide with existing PAM userids in Ambari > metastore will not be migrated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
