[
https://issues.jboss.org/browse/WFLY-1677?page=com.atlassian.jira.plugin....
]
Brian Stansberry updated WFLY-1677:
-----------------------------------
Description:
The SaslPolicyResource attribute all have a default value of "true" but their
handling in the runtime OSH is resulting in "true" not being propagated to the
remoting services if the attribute is undefined. And looking at how org.jboss.sasl works,
it seems that for at least some of these the actual behavior if not set is
"false". So either our metadata is wrong, or the intended value isn't
getting passed to remoting. I expect its the former.
Either way, once the metadata is correct the OSH should be passing the AD's default
value into remoting, not ignoring it.
See
https://github.com/wildfly/wildfly/pull/4733/files#diff-28
was:
The SaslPolicyResource attribute all have a default value of "true" but their
handling in the runtime OSH is resulting in "true" not being propagated to the
remoting services if the attribute is undefined. And looking at how org.jboss.sasl works,
it seems that for at least some of these the actual behavior if not set is
"false". So either our metadata is wrong, or the intended value isn't
getting passed to remoting. I expect its the latter.
Either way, once the metadata is correct the OSH should be passing the AD's default
value into remoting, not ignoring it.
See
https://github.com/wildfly/wildfly/pull/4733/files#diff-28
Suspect handling of SaslPolicyResource attributes
-------------------------------------------------
Key: WFLY-1677
URL:
https://issues.jboss.org/browse/WFLY-1677
Project: WildFly
Issue Type: Bug
Components: Domain Management, Remoting
Reporter: Brian Stansberry
The SaslPolicyResource attribute all have a default value of "true" but their
handling in the runtime OSH is resulting in "true" not being propagated to the
remoting services if the attribute is undefined. And looking at how org.jboss.sasl works,
it seems that for at least some of these the actual behavior if not set is
"false". So either our metadata is wrong, or the intended value isn't
getting passed to remoting. I expect its the former.
Either way, once the metadata is correct the OSH should be passing the AD's default
value into remoting, not ignoring it.
See
https://github.com/wildfly/wildfly/pull/4733/files#diff-28
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira