Project

General

Profile

Bug #6466

Groups Assignment after making some accounts aliases

Added by Jing Tao almost 6 years ago. Updated over 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
-
Target version:
Start date:
03/14/2014
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:

Description

Background: the merge of our ldap trees, the groups information wouldn't be touched.

Before the merge, the uid=ben,o=NCEAS is the member of the group evos; the uid=ben,o=Account is the member of the group dataone.

After the merge, the uid=ben,o=NCEAS is an alias of the uid=ben,ou=Account.

After the merge, i think the group assignment should NOT change. When the user logs in as uid=ben,o=NCEAS, it is still only in the evos group; when the user logs in as uid=ben,ou=Account, it is still only in the dataone group.

Any objection about the above proposal?

Currently, metacat has a different behavior to the above proposal : when the user logs in as uid=ben,o=NCEAS, it is in the dataone group; when the user logs in as uid=ben,ou=Account, it is in the dataone group as well.

History

#1 Updated by Jing Tao almost 6 years ago

I modified the code so metacat wouldn't change the group assignment after the dn was aliased.

So it will work as the above proposal.

#2 Updated by ben leinfelder over 5 years ago

  • Status changed from New to Closed

Jing and I talked about this and I agree with his proposal and implementation.

Also available in: Atom PDF