Ticket #658 (closed Defect: worksforme)

Opened 10 years ago

Last modified 9 years ago

assignment of "admin" in assignToDefaultworkspace aborts if assigned to ANY workspace

Reported by: Malte Owned by: jri
Priority: Major Milestone:
Component: DeepaMehta Standard Distribution Version: 4.3
Keywords: Cc:
Complexity: 1 Area:
Module: deepamehta-accesscontrol



the logging in line 579 (in AccessControlPlugin?.java) described with

// abort if already assigned

should abort ONLY if the assignment is actually related to the defaultWorkspace (URI=de.workspaces.deepamehta) as suggested by method signature assignToDefaultWorkspace ..

This produces subsequent errors when other plugins introduce other workspaces which the "admin" is (by then) already assigned and thus, "admin" never gets assigned to the "DeepaMehta"-Workspace at all (in a fresh installation).

Only way around this is, install custom plugins not directly with initial DM boot.

Change History

comment:1 Changed 10 years ago by Malte

The description should say:

As of now, the implementation of this "wide assignment-check" produces subsequent errors (e.g. missing default assignment of "admin"). The default workspace has an URI, so the assignment-check should be specific and just check for assignments related to a topic with this URI.

comment:2 Changed 9 years ago by jri

In 4.5 this should not happen anymore as there is no assignToDefaultWorkspace() anymore.

Ownership: setting "admin" as the owner of the DeepaMehta workspace is now performed deterministically by an Access Control migration.

Membership: "admin" gets no memberships by default at all as 4.5 doesn't create a Membership association for owners (it would be redundant.)

So, initial booting with installed 3rd-party plugins should not be a problem anymore.

comment:3 Changed 9 years ago by jri

  • Status changed from new to closed
  • Resolution set to worksforme
Note: See TracTickets for help on using tickets.