[
https://issues.jboss.org/browse/WFLY-7462?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-7462:
----------------------------------------
FWIW, I was curious why this would be happening and looked at the elytron code related to
the add op invoked in the reprocer steps to try and see. I saw nothing wrong. Then I tried
to reproduce and couldn't. This was using current WildFly master so perhaps whatever
the issue was has been corrected.
Do not log common CLI failures for Elytron to server log
--------------------------------------------------------
Key: WFLY-7462
URL:
https://issues.jboss.org/browse/WFLY-7462
Project: WildFly
Issue Type: Bug
Components: Security
Affects Versions: 11.0.0.Alpha1
Reporter: Ondrej Lukas
Assignee: Darran Lofthouse
Priority: Critical
Labels: user_experience
Almost every common CLI command failure from Elytron subsystem is logged as ERROR to
server log. For example this means:
* trying to add duplicate resource -> ERROR in server log
* missing required attribute of any resource attribute in CLI command -> ERROR in
server log
* missing capability -> ERROR in server log
* ...
Some reasons why these logs should not be logged to server log:
* Adding useless messages to server log.
* This is inconsistent with other subsystems (e.g. PicketBox). It can be confusing.
These common CLI command failures should be removed from the log, or logged on low level
(i.e. DEBUG)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)