Loading...

XML

Word

Printable

Steps to Reproduce:
Hide

There are many ways how to reproduce it, e.g.:

/subsystem=elytron/properties-realm=realm:add(users-properties={}) { "outcome" => "failed", "failure-description" => "WFLYCTL0155: path may not be null", "rolled-back" => true }

You will see in server log:

ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 56) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "elytron"), ("properties-realm" => "realm") ]) - failure description: "WFLYCTL0155: path may not be null"
Show
There are many ways how to reproduce it, e.g.: /subsystem=elytron/properties-realm=realm:add(users-properties={}) { "outcome" => "failed" , "failure-description" => "WFLYCTL0155: path may not be null " , "rolled-back" => true } You will see in server log: ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 56) WFLYCTL0013: Operation ( "add" ) failed - address: ([ ( "subsystem" => "elytron" ), ( "properties-realm" => "realm" ) ]) - failure description: "WFLYCTL0155: path may not be null "

Almost every common CLI command failure from Elytron subsystem is logged as ERROR to server log. For example this means:

trying to add duplicate service -> 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)

clones

JBEAP-6859 Do not log common CLI failures for Elytron to server log

is blocked by

WFCORE-2249 ObjectTypeValidator only validates fields the user provides

WFCORE-2270 Capability registry should not allow more than one registration point for a RuntimeCapabilityRegistration