[jboss-jira] [JBoss JIRA] (AS7-4587) Remoting subsystem is not consistent with XSD, and not fully exposed in Management API

Misty Stanley-Jones (JIRA) jira-events at lists.jboss.org
Mon Apr 23 01:54:17 EDT 2012


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

        


More information about the jboss-jira mailing list