Ticket #1115 (closed defect: wontfix)

Opened 3 years ago

Last modified 2 years ago

can have two authzgroups with the same name

Reported by: johnlawrenceaspden Owned by:
Priority: awaiting triage Milestone:
Component: ckan Keywords:
Cc: Repository: ckan
Theme: none

Description

If you've got edit permission on an authzgroup, then you can change its name to be the same as another existing authzgroup.

This causes some strange UI effects at worst, and probably causes worse problems somewhere else.

Is there any reason why changing the names of existing authzgroups should be allowed? And if so, name collisions should presumably be guarded against in both the name-changing and creation functions

Change History

comment:1 Changed 3 years ago by thejimmyg

  • Milestone ckan-v1.5 deleted

comment:2 Changed 2 years ago by dread

  • Status changed from new to closed
  • Resolution set to wontfix

Authorization groups deprecated with the Group refactor #1477

Note: See TracTickets for help on using tickets.