[jboss-jira] [JBoss JIRA] (WFLY-7535) filesystem-realm/identity fail-description message should contain new name of resource when name-rewriter is used and exception is related with it.
Hynek Švábek (JIRA)
issues at jboss.org
Wed Nov 9 04:36:02 EST 2016
[ https://issues.jboss.org/browse/WFLY-7535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hynek Švábek updated WFLY-7535:
-------------------------------
Description:
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()
{code}
{
"outcome" => "failed",
"failure-description" => "WFLYELY01000: Identity with name [identity002] already exists.",
"rolled-back" => true
}
{code}
*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."
was:
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 [constantName] already exists. Name-rewriter was used."
> filesystem-realm/identity fail-description message should contain new name of resource when name-rewriter is used and exception is related with it.
> ---------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WFLY-7535
> URL: https://issues.jboss.org/browse/WFLY-7535
> Project: WildFly
> Issue Type: Bug
> Components: Security
> Reporter: Hynek Švábek
> Assignee: Darran Lofthouse
>
> 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()
> {code}
> {
> "outcome" => "failed",
> "failure-description" => "WFLYELY01000: Identity with name [identity002] already exists.",
> "rolled-back" => true
> }
> {code}
> *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."
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
More information about the jboss-jira
mailing list