Actions
Bug #25246
closedUnauthorized access to API should not be logged as error
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
User visibility:
Effort required:
Very Small
Priority:
0
Name check:
To do
Fix check:
Checked
Regression:
No
Description
When we don't have sufficient right to some endpoint, we get an error log :
2024-05-13 09:12:34+0200 ERROR api-processing - Authorization error for 'GET secure/api/user/api/token': User 'toto' is not allowed to access GET secure/api/user/api/token
We should not log an error for this, but rather a warning
Updated by Elaad FURREEDAN 4 months ago
- Status changed from New to In progress
- Assignee set to Elaad FURREEDAN
Updated by Elaad FURREEDAN 4 months ago
- Status changed from In progress to Pending technical review
- Assignee changed from Elaad FURREEDAN to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/5795
Updated by Anonymous 4 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|1a63b2f9e2a7ecfa126df73397cf50fdc03f5e8f.
Updated by Clark ANDRIANASOLO 2 months ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 2 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.1.7 which was released today.
Actions