-
Bug
-
Resolution: Obsolete
-
Critical
-
None
-
7.1.0.DR7
Fail-description message should contain new name of resource when name-rewriter is used and exception is related with it.
Scenario
I want to create "identity" for Elytron filesystem-realm with constant-name-rewriter (or others *-name-rewriter(s) with same behaviour).
I am not able create more then one identity (because name is rewriten to same name).
It is right behaviour but fail-description contains confusing message with OLD resource name.
Steps to reproduce
- /subsystem=elytron/constant-name-rewriter=constantNR001:add(constant=constantName)
- /subsystem=elytron/filesystem-realm=fsRealm123:add(path=fs123, relative-to=jboss.server.config.dir,levels=1, name-rewriter=constantNR001)
- /subsystem=elytron/filesystem-realm=fsRealm123/identity=identity001:add()
I want add second identity with name "identity002" which is rewriten to constantName. I expect fail because the identity with constantName exists.
/subsystem=elytron/filesystem-realm=fsRealm123/identity=identity002:add()
{ "outcome" => "failed", "failure-description" => "WFLYELY01000: Identity with name [identity002] already exists.", "rolled-back" => true }
Suggestion for solution
Message should contain some information about constantName at least. Information about nameRewriter will be also fine.
e.g. "WFLYELY01000: Identity with name [identity002] which was rewritten to [constantName] already exists. Name-rewriter was used."
- is cloned by
-
WFCORE-2372 filesystem-realm/identity fail-description message should contain new name of resource when name-rewriter is used and exception is related with it.
- Resolved