Project

General

Profile

Actions

Bug #11826

closed

Not useful error message on no NCF write access

Bug #11826: Not useful error message on no NCF write access

Added by Janos Mattyasovszky about 8 years ago. Updated almost 4 years ago.

Status:
Resolved
Priority:
N/A
Assignee:
-
Category:
Web - Technique editor
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Operational - other Techniques | Technique editor | Rudder settings
Effort required:
Very Small
Priority:
0
Name check:
Fix check:
Regression:

Description

I tried to use the NCF editor and save something.

I got the error.

An Error occured! Error while creating Technique 'Aaaa'

In the webapp logs I have finally found:

[2017-12-05 16:19:41] ERROR com.normation.rudder.web.rest.RestAuthentication - Authentication API forbids write access to Techniques for user XXXXXX

The user-facing error could be a little bit more descriptive...

Updated by Benoît PECCATTE about 8 years ago Actions #1

  • User visibility changed from First impressions of Rudder to Operational - other Techniques | Technique editor | Rudder settings
  • Priority changed from 80 to 32

The error should be reported by ncf since the api should return a 403.

Updated by Nicolas CHARLES over 6 years ago Actions #2

  • Target version set to 5.0.13
  • Priority changed from 32 to 0

Retargeting to 5.0 to validate if it's still the case

Updated by Vincent MEMBRÉ over 6 years ago Actions #3

  • Target version changed from 5.0.13 to 5.0.14

Updated by Vincent MEMBRÉ about 6 years ago Actions #4

  • Target version changed from 5.0.14 to 5.0.15

Updated by François ARMAND about 6 years ago Actions #5

  • Effort required set to Very Small

budget: very small: it should be corrected by now, try to reproduce and close is the error cause is displayed.

Updated by Vincent MEMBRÉ about 6 years ago Actions #6

  • Target version changed from 5.0.15 to 5.0.16

Updated by Alexis Mousset almost 6 years ago Actions #7

  • Target version changed from 5.0.16 to 5.0.17

Updated by Vincent MEMBRÉ over 5 years ago Actions #8

  • Target version changed from 5.0.17 to 5.0.18

Updated by Vincent MEMBRÉ over 5 years ago Actions #9

  • Target version changed from 5.0.18 to 5.0.19

Updated by Vincent MEMBRÉ over 5 years ago Actions #10

  • Target version changed from 5.0.19 to 5.0.20

Updated by Vincent MEMBRÉ about 5 years ago Actions #11

  • Target version changed from 5.0.20 to 797

Updated by Benoît PECCATTE over 4 years ago Actions #12

  • Target version changed from 797 to 6.1.14

Updated by Vincent MEMBRÉ over 4 years ago Actions #13

  • Target version changed from 6.1.14 to 6.1.15

Updated by Vincent MEMBRÉ over 4 years ago Actions #14

  • Target version changed from 6.1.15 to 6.1.16

Updated by Vincent MEMBRÉ over 4 years ago Actions #15

  • Target version changed from 6.1.16 to 6.1.17

Updated by Vincent MEMBRÉ about 4 years ago Actions #16

  • Target version changed from 6.1.17 to 6.1.18

Updated by Vincent MEMBRÉ almost 4 years ago Actions #17

  • Target version changed from 6.1.18 to 6.1.19

Updated by François ARMAND almost 4 years ago Actions #18

  • Status changed from New to Resolved

Error are now correctly reported.

Actions

Also available in: PDF Atom