[JBoss JIRA] (AS7-4587) Remoting subsystem is not consistent with XSD, and not fully exposed in Management API
7:54 a.m.
Misty Stanley-Jones created AS7-4587:
----------------------------------------
Summary: Remoting subsystem is not consistent with XSD, and not fully exposed
in Management API
Key: AS7-4587
URL: https://issues.jboss.org/browse/AS7-4587
Project: Application Server 7
Issue Type: Bug
Components: Remoting
Affects Versions: 7.1.1.Final
Reporter: Misty Stanley-Jones
Assignee: David Lloyd
1. The XSD says that at the authentication-provider is an element:
<authentication-provider name="myprovider" />
However, the Management GUI will only change it with a command like the following, which
is operating on an attribute:
/profile=default/subsystem=remoting/connector=remoting-connector/:write-attribute(name=authentication-provider,value=myProvider)
2. The <sasl> element of the <connector> element of the remoting subsystem is
not exposed in the Management API. I cannot find a way to add it to the CLI at all. Here
is the configuration which I pasted into my domain.xml to get it working.
<sasl>
<include-mechanisms value="GSSAPI PLAIN DIGEST-MD5" />
<qop value="auth" />
<strength value="medium" />
<reuse-session value="false" />
<server-auth value="false" />
<policy>
<forward-secrecy value="true" />
<no-active value="false" />
<no-anonymous value="false" />
<no-dictionary value="true" />
<no-plain-text value="false" />
<pass-credentials value="true" />
</policy>
<properties>
<property name="myprop1" value="1" />
<property name="myprop2" value="2" />
</properties>
</sasl>
3. Individual properties under the <properties> elements of <connector> and
<sasl> will not allow me to have only a name, but requires a value as well.
Here is an entire subsystem configuration which seems to work (at least the server
starts). I do not have the infrastructure of skills to test it thoroughly.
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<connector name="remoting-connector"
socket-binding="remoting" \
security-realm="ApplicationRealm">
<authentication-provider name="myprovider"/>
<properties>
<property name="myprop3" value="baz"/>
</properties>
<sasl>
<include-mechanisms value="GSSAPI PLAIN
DIGEST-MD5"/>
<qop value="auth"/>
<strength value="medium"/>
<server-auth value="false"/>
<reuse-session value="false"/>
<policy>
<forward-secrecy value="true"/>
<no-active value="false"/>
<no-anonymous value="false"/>
<no-dictionary value="true"/>
<no-plain-text value="false"/>
<pass-credentials value="true"/>
</policy>
<properties>
<property name="myprop1"
value="1"/>
<property name="myprop2"
value="2"/>
</properties>
</sasl>
</connector>
<outbound-connections>
<outbound-connection name="my-outbound-connection"
uri="http://myhost:7777/"/>
<remote-outbound-connection name="my-remote-connection"
outbound-socket-binding-ref="my-remote-socket" username="myUser"
security-realm="myRealm"/>
<local-outbound-connection name="myLocalConnection"
outbound-socket-binding-ref="my-outbound-socket"/>
</outbound-connections>
</subsystem>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:55 p.m.
[
https://issues.jboss.org/browse/AS7-4587?page=com.atlassian.jira.plugin.s...
]
David Lloyd commented on AS7-4587:
----------------------------------
You should be aware that something can be a management *attribute* but still be
represented in XML by an *element* - in fact this is quite common. Also XML elements such
as "<sasl>" which exist to categorize other XML elements may not have a
representation within the model (instead the management attributes and resources they
contain would be direct children of the enclosing management element, in this case the
connector).
Remoting subsystem is not consistent with XSD, and not fully exposed
in Management API
--------------------------------------------------------------------------------------
Key: AS7-4587
URL: https://issues.jboss.org/browse/AS7-4587
Project: Application Server 7
Issue Type: Bug
Components: Remoting
Affects Versions: 7.1.1.Final
Reporter: Misty Stanley-Jones
Assignee: David Lloyd
1. The XSD says that at the authentication-provider is an element:
<authentication-provider name="myprovider" />
However, the Management GUI will only change it with a command like the following, which
is operating on an attribute:
/profile=default/subsystem=remoting/connector=remoting-connector/:write-attribute(name=authentication-provider,value=myProvider)
2. The <sasl> element of the <connector> element of the remoting subsystem is
not exposed in the Management API. I cannot find a way to add it to the CLI at all. Here
is the configuration which I pasted into my domain.xml to get it working.
<sasl>
<include-mechanisms value="GSSAPI PLAIN DIGEST-MD5" />
<qop value="auth" />
<strength value="medium" />
<reuse-session value="false" />
<server-auth value="false" />
<policy>
<forward-secrecy value="true" />
<no-active value="false" />
<no-anonymous value="false" />
<no-dictionary value="true" />
<no-plain-text value="false" />
<pass-credentials value="true" />
</policy>
<properties>
<property name="myprop1" value="1" />
<property name="myprop2" value="2" />
</properties>
</sasl>
3. Individual properties under the <properties> elements of <connector> and
<sasl> will not allow me to have only a name, but requires a value as well.
Here is an entire subsystem configuration which seems to work (at least the server
starts). I do not have the infrastructure of skills to test it thoroughly.
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<connector name="remoting-connector"
socket-binding="remoting" \
security-realm="ApplicationRealm">
<authentication-provider name="myprovider"/>
<properties>
<property name="myprop3" value="baz"/>
</properties>
<sasl>
<include-mechanisms value="GSSAPI PLAIN
DIGEST-MD5"/>
<qop value="auth"/>
<strength value="medium"/>
<server-auth value="false"/>
<reuse-session value="false"/>
<policy>
<forward-secrecy value="true"/>
<no-active value="false"/>
<no-anonymous value="false"/>
<no-dictionary value="true"/>
<no-plain-text value="false"/>
<pass-credentials value="true"/>
</policy>
<properties>
<property name="myprop1"
value="1"/>
<property name="myprop2"
value="2"/>
</properties>
</sasl>
</connector>
<outbound-connections>
<outbound-connection name="my-outbound-connection"
uri="http://myhost:7777/"/>
<remote-outbound-connection name="my-remote-connection"
outbound-socket-binding-ref="my-remote-socket" username="myUser"
security-realm="myRealm"/>
<local-outbound-connection name="myLocalConnection"
outbound-socket-binding-ref="my-outbound-socket"/>
</outbound-connections>
</subsystem>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:33 p.m.
[
https://issues.jboss.org/browse/AS7-4587?page=com.atlassian.jira.plugin.s...
]
David Lloyd reassigned AS7-4587:
--------------------------------
Assignee: Misty Stanley-Jones (was: David Lloyd)
Let me know if you determine that there is something missing beyond the cases I outlined
above.
Remoting subsystem is not consistent with XSD, and not fully exposed
in Management API
--------------------------------------------------------------------------------------
Key: AS7-4587
URL: https://issues.jboss.org/browse/AS7-4587
Project: Application Server 7
Issue Type: Bug
Components: Remoting
Affects Versions: 7.1.1.Final
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
1. The XSD says that at the authentication-provider is an element:
<authentication-provider name="myprovider" />
However, the Management GUI will only change it with a command like the following, which
is operating on an attribute:
/profile=default/subsystem=remoting/connector=remoting-connector/:write-attribute(name=authentication-provider,value=myProvider)
2. The <sasl> element of the <connector> element of the remoting subsystem is
not exposed in the Management API. I cannot find a way to add it to the CLI at all. Here
is the configuration which I pasted into my domain.xml to get it working.
<sasl>
<include-mechanisms value="GSSAPI PLAIN DIGEST-MD5" />
<qop value="auth" />
<strength value="medium" />
<reuse-session value="false" />
<server-auth value="false" />
<policy>
<forward-secrecy value="true" />
<no-active value="false" />
<no-anonymous value="false" />
<no-dictionary value="true" />
<no-plain-text value="false" />
<pass-credentials value="true" />
</policy>
<properties>
<property name="myprop1" value="1" />
<property name="myprop2" value="2" />
</properties>
</sasl>
3. Individual properties under the <properties> elements of <connector> and
<sasl> will not allow me to have only a name, but requires a value as well.
Here is an entire subsystem configuration which seems to work (at least the server
starts). I do not have the infrastructure of skills to test it thoroughly.
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<connector name="remoting-connector"
socket-binding="remoting" \
security-realm="ApplicationRealm">
<authentication-provider name="myprovider"/>
<properties>
<property name="myprop3" value="baz"/>
</properties>
<sasl>
<include-mechanisms value="GSSAPI PLAIN
DIGEST-MD5"/>
<qop value="auth"/>
<strength value="medium"/>
<server-auth value="false"/>
<reuse-session value="false"/>
<policy>
<forward-secrecy value="true"/>
<no-active value="false"/>
<no-anonymous value="false"/>
<no-dictionary value="true"/>
<no-plain-text value="false"/>
<pass-credentials value="true"/>
</policy>
<properties>
<property name="myprop1"
value="1"/>
<property name="myprop2"
value="2"/>
</properties>
</sasl>
</connector>
<outbound-connections>
<outbound-connection name="my-outbound-connection"
uri="http://myhost:7777/"/>
<remote-outbound-connection name="my-remote-connection"
outbound-socket-binding-ref="my-remote-socket" username="myUser"
security-realm="myRealm"/>
<local-outbound-connection name="myLocalConnection"
outbound-socket-binding-ref="my-outbound-socket"/>
</outbound-connections>
</subsystem>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:21 p.m.
[
https://issues.jboss.org/browse/AS7-4587?page=com.atlassian.jira.plugin.s...
]
David Lloyd reassigned AS7-4587:
--------------------------------
Assignee: Darran Lofthouse (was: Misty Stanley-Jones)
Darran, can you address the question?
Thanks.
Remoting subsystem is not consistent with XSD, and not fully exposed
in Management API
--------------------------------------------------------------------------------------
Key: AS7-4587
URL: https://issues.jboss.org/browse/AS7-4587
Project: Application Server 7
Issue Type: Bug
Components: Remoting
Affects Versions: 7.1.1.Final
Reporter: Misty Stanley-Jones
Assignee: Darran Lofthouse
1. The XSD says that at the authentication-provider is an element:
<authentication-provider name="myprovider" />
However, the Management GUI will only change it with a command like the following, which
is operating on an attribute:
/profile=default/subsystem=remoting/connector=remoting-connector/:write-attribute(name=authentication-provider,value=myProvider)
2. The <sasl> element of the <connector> element of the remoting subsystem is
not exposed in the Management API. I cannot find a way to add it to the CLI at all. Here
is the configuration which I pasted into my domain.xml to get it working.
<sasl>
<include-mechanisms value="GSSAPI PLAIN DIGEST-MD5" />
<qop value="auth" />
<strength value="medium" />
<reuse-session value="false" />
<server-auth value="false" />
<policy>
<forward-secrecy value="true" />
<no-active value="false" />
<no-anonymous value="false" />
<no-dictionary value="true" />
<no-plain-text value="false" />
<pass-credentials value="true" />
</policy>
<properties>
<property name="myprop1" value="1" />
<property name="myprop2" value="2" />
</properties>
</sasl>
3. Individual properties under the <properties> elements of <connector> and
<sasl> will not allow me to have only a name, but requires a value as well.
Here is an entire subsystem configuration which seems to work (at least the server
starts). I do not have the infrastructure of skills to test it thoroughly.
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<connector name="remoting-connector"
socket-binding="remoting" \
security-realm="ApplicationRealm">
<authentication-provider name="myprovider"/>
<properties>
<property name="myprop3" value="baz"/>
</properties>
<sasl>
<include-mechanisms value="GSSAPI PLAIN
DIGEST-MD5"/>
<qop value="auth"/>
<strength value="medium"/>
<server-auth value="false"/>
<reuse-session value="false"/>
<policy>
<forward-secrecy value="true"/>
<no-active value="false"/>
<no-anonymous value="false"/>
<no-dictionary value="true"/>
<no-plain-text value="false"/>
<pass-credentials value="true"/>
</policy>
<properties>
<property name="myprop1"
value="1"/>
<property name="myprop2"
value="2"/>
</properties>
</sasl>
</connector>
<outbound-connections>
<outbound-connection name="my-outbound-connection"
uri="http://myhost:7777/"/>
<remote-outbound-connection name="my-remote-connection"
outbound-socket-binding-ref="my-remote-socket" username="myUser"
security-realm="myRealm"/>
<local-outbound-connection name="myLocalConnection"
outbound-socket-binding-ref="my-outbound-socket"/>
</outbound-connections>
</subsystem>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:25 p.m.
[
https://issues.jboss.org/browse/AS7-4587?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse updated AS7-4587:
----------------------------------
Fix Version/s: 7.1.2.Final-redhat1
Remoting subsystem is not consistent with XSD, and not fully exposed
in Management API
--------------------------------------------------------------------------------------
Key: AS7-4587
URL: https://issues.jboss.org/browse/AS7-4587
Project: Application Server 7
Issue Type: Bug
Components: Remoting
Affects Versions: 7.1.1.Final
Reporter: Misty Stanley-Jones
Assignee: Darran Lofthouse
Fix For: 7.1.2.Final-redhat1
1. The XSD says that at the authentication-provider is an element:
<authentication-provider name="myprovider" />
However, the Management GUI will only change it with a command like the following, which
is operating on an attribute:
/profile=default/subsystem=remoting/connector=remoting-connector/:write-attribute(name=authentication-provider,value=myProvider)
2. The <sasl> element of the <connector> element of the remoting subsystem is
not exposed in the Management API. I cannot find a way to add it to the CLI at all. Here
is the configuration which I pasted into my domain.xml to get it working.
<sasl>
<include-mechanisms value="GSSAPI PLAIN DIGEST-MD5" />
<qop value="auth" />
<strength value="medium" />
<reuse-session value="false" />
<server-auth value="false" />
<policy>
<forward-secrecy value="true" />
<no-active value="false" />
<no-anonymous value="false" />
<no-dictionary value="true" />
<no-plain-text value="false" />
<pass-credentials value="true" />
</policy>
<properties>
<property name="myprop1" value="1" />
<property name="myprop2" value="2" />
</properties>
</sasl>
3. Individual properties under the <properties> elements of <connector> and
<sasl> will not allow me to have only a name, but requires a value as well.
Here is an entire subsystem configuration which seems to work (at least the server
starts). I do not have the infrastructure of skills to test it thoroughly.
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<connector name="remoting-connector"
socket-binding="remoting" \
security-realm="ApplicationRealm">
<authentication-provider name="myprovider"/>
<properties>
<property name="myprop3" value="baz"/>
</properties>
<sasl>
<include-mechanisms value="GSSAPI PLAIN
DIGEST-MD5"/>
<qop value="auth"/>
<strength value="medium"/>
<server-auth value="false"/>
<reuse-session value="false"/>
<policy>
<forward-secrecy value="true"/>
<no-active value="false"/>
<no-anonymous value="false"/>
<no-dictionary value="true"/>
<no-plain-text value="false"/>
<pass-credentials value="true"/>
</policy>
<properties>
<property name="myprop1"
value="1"/>
<property name="myprop2"
value="2"/>
</properties>
</sasl>
</connector>
<outbound-connections>
<outbound-connection name="my-outbound-connection"
uri="http://myhost:7777/"/>
<remote-outbound-connection name="my-remote-connection"
outbound-socket-binding-ref="my-remote-socket" username="myUser"
security-realm="myRealm"/>
<local-outbound-connection name="myLocalConnection"
outbound-socket-binding-ref="my-outbound-socket"/>
</outbound-connections>
</subsystem>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:36 p.m.
[
https://issues.jboss.org/browse/AS7-4587?page=com.atlassian.jira.plugin.s...
]
Darran Lofthouse updated AS7-4587:
----------------------------------
Fix Version/s: (was: 7.1.2.Final (EAP))
Assignee: Misty Stanley-Jones (was: Darran Lofthouse)
Here are the commands I have just run through the CLI to build up the configuration you
were able to define in XML: -
/subsystem=remoting/connector=remoting-connector/security=sasl:add
/subsystem=remoting/connector=remoting-connector/security=sasl:write-attribute(name=include-mechanisms,value=["DIGEST","PLAIN","GSSAPI"])
/subsystem=remoting/connector=remoting-connector/security=sasl:write-attribute(name=qop,value=["auth"])
/subsystem=remoting/connector=remoting-connector/security=sasl:write-attribute(name=strength,value=["medium"])
/subsystem=remoting/connector=remoting-connector/security=sasl:write-attribute(name=server-auth,value=false)
/subsystem=remoting/connector=remoting-connector/security=sasl:write-attribute(name=reuse-session,value=false)
/subsystem=remoting/connector=remoting-connector/security=sasl/sasl-policy=policy:add
/subsystem=remoting/connector=remoting-connector/security=sasl/sasl-policy=policy:write-attribute(name=forward-secrecy,value=true)
/subsystem=remoting/connector=remoting-connector/security=sasl/sasl-policy=policy:write-attribute(name=no-active,value=false)
/subsystem=remoting/connector=remoting-connector/security=sasl/sasl-policy=policy:write-attribute(name=no-dictionary,value=true)
/subsystem=remoting/connector=remoting-connector/security=sasl/sasl-policy=policy:write-attribute(name=no-plain-text,value=false)
/subsystem=remoting/connector=remoting-connector/security=sasl/sasl-policy=policy:write-attribute(name=pass-credentials,value=true)
/subsystem=remoting/connector=remoting-connector/security=sasl/property=myprop:add(value=1)
/subsystem=remoting/connector=remoting-connector/security=sasl/property=myprop2:add(value=2)
Remoting subsystem is not consistent with XSD, and not fully exposed
in Management API
--------------------------------------------------------------------------------------
Key: AS7-4587
URL: https://issues.jboss.org/browse/AS7-4587
Project: Application Server 7
Issue Type: Bug
Components: Remoting
Affects Versions: 7.1.1.Final
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
1. The XSD says that at the authentication-provider is an element:
<authentication-provider name="myprovider" />
However, the Management GUI will only change it with a command like the following, which
is operating on an attribute:
/profile=default/subsystem=remoting/connector=remoting-connector/:write-attribute(name=authentication-provider,value=myProvider)
2. The <sasl> element of the <connector> element of the remoting subsystem is
not exposed in the Management API. I cannot find a way to add it to the CLI at all. Here
is the configuration which I pasted into my domain.xml to get it working.
<sasl>
<include-mechanisms value="GSSAPI PLAIN DIGEST-MD5" />
<qop value="auth" />
<strength value="medium" />
<reuse-session value="false" />
<server-auth value="false" />
<policy>
<forward-secrecy value="true" />
<no-active value="false" />
<no-anonymous value="false" />
<no-dictionary value="true" />
<no-plain-text value="false" />
<pass-credentials value="true" />
</policy>
<properties>
<property name="myprop1" value="1" />
<property name="myprop2" value="2" />
</properties>
</sasl>
3. Individual properties under the <properties> elements of <connector> and
<sasl> will not allow me to have only a name, but requires a value as well.
Here is an entire subsystem configuration which seems to work (at least the server
starts). I do not have the infrastructure of skills to test it thoroughly.
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<connector name="remoting-connector"
socket-binding="remoting" \
security-realm="ApplicationRealm">
<authentication-provider name="myprovider"/>
<properties>
<property name="myprop3" value="baz"/>
</properties>
<sasl>
<include-mechanisms value="GSSAPI PLAIN
DIGEST-MD5"/>
<qop value="auth"/>
<strength value="medium"/>
<server-auth value="false"/>
<reuse-session value="false"/>
<policy>
<forward-secrecy value="true"/>
<no-active value="false"/>
<no-anonymous value="false"/>
<no-dictionary value="true"/>
<no-plain-text value="false"/>
<pass-credentials value="true"/>
</policy>
<properties>
<property name="myprop1"
value="1"/>
<property name="myprop2"
value="2"/>
</properties>
</sasl>
</connector>
<outbound-connections>
<outbound-connection name="my-outbound-connection"
uri="http://myhost:7777/"/>
<remote-outbound-connection name="my-remote-connection"
outbound-socket-binding-ref="my-remote-socket" username="myUser"
security-realm="myRealm"/>
<local-outbound-connection name="myLocalConnection"
outbound-socket-binding-ref="my-outbound-socket"/>
</outbound-connections>
</subsystem>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:54 a.m.
[
https://issues.jboss.org/browse/AS7-4587?page=com.atlassian.jira.plugin.s...
]
Misty Stanley-Jones commented on AS7-4587:
------------------------------------------
Beautiful work. Thank you!
Remoting subsystem is not consistent with XSD, and not fully exposed
in Management API
--------------------------------------------------------------------------------------
Key: AS7-4587
URL: https://issues.jboss.org/browse/AS7-4587
Project: Application Server 7
Issue Type: Bug
Components: Remoting
Affects Versions: 7.1.1.Final
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
1. The XSD says that at the authentication-provider is an element:
<authentication-provider name="myprovider" />
However, the Management GUI will only change it with a command like the following, which
is operating on an attribute:
/profile=default/subsystem=remoting/connector=remoting-connector/:write-attribute(name=authentication-provider,value=myProvider)
2. The <sasl> element of the <connector> element of the remoting subsystem is
not exposed in the Management API. I cannot find a way to add it to the CLI at all. Here
is the configuration which I pasted into my domain.xml to get it working.
<sasl>
<include-mechanisms value="GSSAPI PLAIN DIGEST-MD5" />
<qop value="auth" />
<strength value="medium" />
<reuse-session value="false" />
<server-auth value="false" />
<policy>
<forward-secrecy value="true" />
<no-active value="false" />
<no-anonymous value="false" />
<no-dictionary value="true" />
<no-plain-text value="false" />
<pass-credentials value="true" />
</policy>
<properties>
<property name="myprop1" value="1" />
<property name="myprop2" value="2" />
</properties>
</sasl>
3. Individual properties under the <properties> elements of <connector> and
<sasl> will not allow me to have only a name, but requires a value as well.
Here is an entire subsystem configuration which seems to work (at least the server
starts). I do not have the infrastructure of skills to test it thoroughly.
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<connector name="remoting-connector"
socket-binding="remoting" \
security-realm="ApplicationRealm">
<authentication-provider name="myprovider"/>
<properties>
<property name="myprop3" value="baz"/>
</properties>
<sasl>
<include-mechanisms value="GSSAPI PLAIN
DIGEST-MD5"/>
<qop value="auth"/>
<strength value="medium"/>
<server-auth value="false"/>
<reuse-session value="false"/>
<policy>
<forward-secrecy value="true"/>
<no-active value="false"/>
<no-anonymous value="false"/>
<no-dictionary value="true"/>
<no-plain-text value="false"/>
<pass-credentials value="true"/>
</policy>
<properties>
<property name="myprop1"
value="1"/>
<property name="myprop2"
value="2"/>
</properties>
</sasl>
</connector>
<outbound-connections>
<outbound-connection name="my-outbound-connection"
uri="http://myhost:7777/"/>
<remote-outbound-connection name="my-remote-connection"
outbound-socket-binding-ref="my-remote-socket" username="myUser"
security-realm="myRealm"/>
<local-outbound-connection name="myLocalConnection"
outbound-socket-binding-ref="my-outbound-socket"/>
</outbound-connections>
</subsystem>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:56 a.m.
[
https://issues.jboss.org/browse/AS7-4587?page=com.atlassian.jira.plugin.s...
]
Misty Stanley-Jones resolved AS7-4587.
--------------------------------------
Fix Version/s: 7.1.3.Final (EAP)
Resolution: Done
Remoting subsystem is not consistent with XSD, and not fully exposed
in Management API
--------------------------------------------------------------------------------------
Key: AS7-4587
URL: https://issues.jboss.org/browse/AS7-4587
Project: Application Server 7
Issue Type: Bug
Components: Remoting
Affects Versions: 7.1.1.Final
Reporter: Misty Stanley-Jones
Assignee: Misty Stanley-Jones
Fix For: 7.1.3.Final (EAP)
1. The XSD says that at the authentication-provider is an element:
<authentication-provider name="myprovider" />
However, the Management GUI will only change it with a command like the following, which
is operating on an attribute:
/profile=default/subsystem=remoting/connector=remoting-connector/:write-attribute(name=authentication-provider,value=myProvider)
2. The <sasl> element of the <connector> element of the remoting subsystem is
not exposed in the Management API. I cannot find a way to add it to the CLI at all. Here
is the configuration which I pasted into my domain.xml to get it working.
<sasl>
<include-mechanisms value="GSSAPI PLAIN DIGEST-MD5" />
<qop value="auth" />
<strength value="medium" />
<reuse-session value="false" />
<server-auth value="false" />
<policy>
<forward-secrecy value="true" />
<no-active value="false" />
<no-anonymous value="false" />
<no-dictionary value="true" />
<no-plain-text value="false" />
<pass-credentials value="true" />
</policy>
<properties>
<property name="myprop1" value="1" />
<property name="myprop2" value="2" />
</properties>
</sasl>
3. Individual properties under the <properties> elements of <connector> and
<sasl> will not allow me to have only a name, but requires a value as well.
Here is an entire subsystem configuration which seems to work (at least the server
starts). I do not have the infrastructure of skills to test it thoroughly.
<subsystem xmlns="urn:jboss:domain:remoting:1.1">
<connector name="remoting-connector"
socket-binding="remoting" \
security-realm="ApplicationRealm">
<authentication-provider name="myprovider"/>
<properties>
<property name="myprop3" value="baz"/>
</properties>
<sasl>
<include-mechanisms value="GSSAPI PLAIN
DIGEST-MD5"/>
<qop value="auth"/>
<strength value="medium"/>
<server-auth value="false"/>
<reuse-session value="false"/>
<policy>
<forward-secrecy value="true"/>
<no-active value="false"/>
<no-anonymous value="false"/>
<no-dictionary value="true"/>
<no-plain-text value="false"/>
<pass-credentials value="true"/>
</policy>
<properties>
<property name="myprop1"
value="1"/>
<property name="myprop2"
value="2"/>
</properties>
</sasl>
</connector>
<outbound-connections>
<outbound-connection name="my-outbound-connection"
uri="http://myhost:7777/"/>
<remote-outbound-connection name="my-remote-connection"
outbound-socket-binding-ref="my-remote-socket" username="myUser"
security-realm="myRealm"/>
<local-outbound-connection name="myLocalConnection"
outbound-socket-binding-ref="my-outbound-socket"/>
</outbound-connections>
</subsystem>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
4435
days inactive
4453
days old
7 comments
3 participants
participants (3)
-
Darran Lofthouse (JIRA) -
David Lloyd (JIRA)
-
Misty Stanley-Jones (JIRA)