Ticket #334 (closed Defect: fixed)
newly created user_account cannot "create"..
| Reported by: | Malte | Owned by: | |
|---|---|---|---|
| Priority: | Major | Milestone: | |
| Component: | DeepaMehta Standard Distribution | Version: | 4.0.12 |
| Keywords: | Cc: | ||
| Complexity: | 3 | Area: | GUI / Usability |
| Module: | deepamehta-webclient |
Description
a newly created user_account cannot create a new topicmap and does not see the create menu despite being logged in.
how does a proper "membership"-association has to look like, maybe this is what`s missing since i didnt set one explicitly. though implicitly the newly created user_account has an aggregation, where the user_account topic plays the "whole"-role and the "workpsace x" plays the part role. is this sufficient or must there alsp be a relationship between username and workspace?
maybe this ticket is related to recently discovered error logged in #333
Change History
comment:2 Changed 12 years ago by Malte
- Status changed from new to closed
- Resolution set to fixed
Thanks for your quick support, the create menu shows up. This issue seems to be unrelated to #333, though.
comment:3 Changed 12 years ago by jri
Some more general info about access control:
For a user to create a topicmap (resp. any type) these requirements must be met:
- The logged in user is a member of a workspace the type Topicmap (resp. any type) is assigned to.
By default the type Topicmap (resp. any type of the DM Standard Distribution) is assigned to the workspace "DeepaMehta".
If you use a custom workspace you have to assign the type Topicmap to that workspace manually (interactively or via migration).
- The type Topicmap has an ACL entry for the Member role and Write permission.
By default the type Topicmap (resp. any type of the DM Standard Distribution) has that ACL entry.
Newly created types (interactively or via migration) get this ACL entry automatically.
=> Check if your custom workspace has the Topicmap assignment.
This is a regular workspace assignment: an Aggregation from topic type Topicmap (whole) to the workspace (part)
All access control configurations involve the Username topic, not the User Account topic.
So, a workspace membership consists of an aggregation from the Username (whole) to the Workspace (part).
All topics -- including their child topics -- created by the Webclient are automatically assigned to the current workspace.
So, when you create an User Account in the Webclient its Username topic gets the Workspace assignment automatically.
Wenn you create an User Account with another client (via the REST API) you must set the dm4_workspace_id cookie to the current workspace. Otherwise there will be no autmatic workspace assignment. You can create the workspace assignment manually, though.