Project

General

Profile

Actions

bug #6886

closed

Entity creation for users having only CREATE may fail in long running conversations

Added by Andreas Kohlbecker over 6 years ago. Updated over 6 years ago.

Status:
Duplicate
Priority:
New
Category:
cdmlib
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Severity:
normal
Found in Version:
Tags:

Description

I observed the following problems while implementing the ExtendedCreatePermissionManager for #6867

when this sequence is used (snipped from CdmStore.java):


T mergedBean = mergedBean(bean);
repo.getCommonService().save(mergedBean);
session.flush();

the flush causes the bean being saved a second time, since hibernate assumes that the entity is dirty and schedules a save operation. For this save the user would need the UPDATE permission, and the save operation fails.


Related issues

Related to EDIT - feature request #4305: newly created entities must stay editable even if a user only has the permission to create themIn ProgressAndreas Kohlbecker

Actions
Related to EDIT - feature request #6867: explicitely assign and revoke UPDATE & DELETE permission per enitity in the registration workflow ClosedAndreas Kohlbecker

Actions
Related to EDIT - bug #6885: UserService.loadUserByUsername() cannot find user in long running sessionNewAndreas Müller

Actions
Is duplicate of EDIT - bug #7021: CREATE permission not sufficient to save new TaxonName entityResolvedAndreas Müller

Actions
Actions

Also available in: Atom PDF