Project

General

Profile

Actions

bug #4299

open

Show error when permission is denied ...

Added by Andreas Müller over 7 years ago. Updated 9 months ago.

Status:
New
Priority:
New
Assignee:
Category:
taxeditor
Target version:
Start date:
08/05/2014
Due date:
% Done:

0%

Estimated time:
Severity:
normal
Found in Version:

Description

... or don't allow opening "New Classification" dialog if user is not allowed to create a new classification.

A user who has no rights to create a taxon node may currently still open the New Classification dialog. Pressing the Finish button there gives no result except for an exception being logged but not shown to the user.

So there are 2 problems:

  1. Exceptions should always be shown to the user

  2. If a user is not allowed to create a classification (AND its root node, which is always created), he/she should not be allowed to open the dialog at all

Actions #1

Updated by Andreas Kohlbecker over 7 years ago

  • Keywords set to permission security
Actions #2

Updated by Andreas Kohlbecker over 5 years ago

  • Tags changed from permission security to permission, security
  • Description updated (diff)
Actions #3

Updated by Andreas Müller almost 2 years ago

  • Assignee changed from Andreas Kohlbecker to Katja Luther
  • Target version changed from 120 to Release 5.15

I move this to current milestone as we have more and more DBs with limited rights and therefore this issue becomes more relevant. Please move to other milestone if it should be handled later.
Also I change owner as these issues are now handled by KL.

Actions #4

Updated by Andreas Müller almost 2 years ago

Also entering the New->Taxon dialog should not be possible as the dialog is fully disabled in this case anyway (but only if the user has no rights on the current subtree, so maybe this is another issue).

Actions #5

Updated by Andreas Müller almost 2 years ago

  • Private changed from Yes to No
Actions #6

Updated by Andreas Kohlbecker almost 2 years ago

  • Description updated (diff)

I think we should change the subject of this issue to better reflect the details of this task.

Suggestion: Adapt "New Classification" actions and UI-elements to missing TAXON_NODE permissions

Actions #7

Updated by Andreas Müller almost 2 years ago

I think I chose this title because my concern was that permission errors are not shown in general (or at least at multiple places). If this is not the case and if the exception is swallowed only here we should ofcourse change the title.

Actions #8

Updated by Katja Luther over 1 year ago

  • Target version changed from Release 5.15 to Release 5.18
Actions #9

Updated by Katja Luther about 1 year ago

  • Target version changed from Release 5.18 to Release 5.19
Actions #10

Updated by Andreas Müller 12 months ago

  • Target version changed from Release 5.19 to Release 5.21
Actions #11

Updated by Andreas Müller 11 months ago

  • Target version changed from Release 5.21 to Release 5.22
Actions #12

Updated by Katja Luther 9 months ago

  • Target version changed from Release 5.22 to Release 5.30
Actions

Also available in: Atom PDF