Ticket #2075 (new defect)

Opened 10 years ago

Last modified 10 years ago

New subgroups system should accept inconsistent upgraded conf

Reported by: gracinet Owned by: gracinet
Priority: P2 Milestone: CPS 3.5.7
Component: CPSUserFolder Version: TRUNK
Severity: major Keywords: nested groups ldap upgrade meta
Cc:

Description (last modified by gracinet) (diff)

The new subgroups system of #1402 is deactivated by default, simply by having empty field names for subgroups and supergroups.

But, for instances whose regular upgrade path starts with reimporting CPSDefault, of course these field names aren't empty, so the system is in use. In case groups are mounted from LDAP, or more complicated setups, the corresponding fields won't work right away.

Now the problem is that in case the fields for sub/super groups don't work, the groups system is broken, the list of groups of all users behave as empty.

Conclusion : for people who don't care about nested groups, the system should work as before the upgrade, with a proper warning.

CPSLDAPSetup's profile with LDAP groups should be updated to work (without nested groups)

Change History

comment:1 Changed 10 years ago by gracinet

  • Description modified (diff)

CPSLDAPSetup now up to date [54038]

Note: See TracTickets for help on using tickets.