[
https://issues.jboss.org/browse/WFLY-8238?page=com.atlassian.jira.plugin....
]
Brian Stansberry commented on WFLY-8238:
----------------------------------------
[~thofman] I haven't looked at the code involved here at all, but just as an FYI -- we
only added overall validation of requires and alternatives into the kernel in the last
couple years. (See ValidateModelStepHandler in WildFly Core.) So since that didn't
exist for years, there's a fair amount of custom validation code scattered around the
code base from when devs saw a particular need for some validation check. When you find
that kind of thing, and it sounds like you have here, it's best to investigate with
the component lead whether the validation is meant to do anything different from what the
kernel now does. If it isn't, strongly consider stripping it out and relying on the
kernel.
Unable to undefine credential-reference
---------------------------------------
Key: WFLY-8238
URL:
https://issues.jboss.org/browse/WFLY-8238
Project: WildFly
Issue Type: Bug
Components: JMS, Security
Reporter: Claudio Miranda
Assignee: Tomas Hofman
A bridge is added and a credential-reference is set.
However a "password" attribute cannot be set as the alternatives constraint
validates the data, but the password attribute has a default value.
Also neither credential-reference and password are required=true, so they may be
undefined.
{code}
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ)
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:write-attribute(name=credential-reference,value={clear-text=senha1})
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=credential-reference)
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" =>
"WFLYMSGAMQ0069: Attribute (credential-reference) can not been undefined as the
resource does not define any alternative to this attribute."},
"rolled-back" => true
}
{code}
The same problem, when user adds a bridge with a password and later wants to undefine it
to add a credential-reference
{code}
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:add(discovery-group=mane,queue-name=DLQ,forwarding-address=DLQ,password=senha1)
/profile=full/subsystem=messaging-activemq/server=default/bridge=test1:undefine-attribute(name=password)
{
"outcome" => "failed",
"failure-description" => {"domain-failure-description" =>
"WFLYMSGAMQ0069: Attribute (password) can not been undefined as the resource does not
define any alternative to this attribute."},
"rolled-back" => true
}
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)