[jboss-jira] [JBoss JIRA] (WFLY-7309) Make the authentication configurable in the eap testsuite

[Filippe Spolti (JIRA)]

     [ https://issues.jboss.org/browse/WFLY-7309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Filippe Spolti updated WFLY-7309:
---------------------------------
    Description: 
Actually some tests cases fails when running against a remote eap instance. 

In this specific case instances running on Openshift v3.
In order to get those tests working we have to modify some classes to configure the authentication.
Example: 

org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this:

{code:java}
    private MBeanServerConnection getMBeanServerConnection() throws IOException {
        final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
        connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address));
        return connector.getMBeanServerConnection();

    }
{code}

To:

{code:java}

    private MBeanServerConnection getMBeanServerConnection() throws IOException {
        HashMap<String, String[]> propEnv = new HashMap<String, String[]>();
        String[] credentials = {  System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") };
        propEnv.put(JMXConnector.CREDENTIALS, credentials);
        final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
        connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv);
        return connector.getMBeanServerConnection();
    }
{code}


Could these kind of authentication being configurable?
It is important to us because this allows the tests to be executed against the docker images running in openshift.

  was:
Actually some tests cases of EAP's testsuite failes when running against a remote eap instance. 

In this specific case, EAP 6/7 instances running on Openshift v3.
In order to get those tests working we have to modify some classes to configure the authentication.
Example: 

org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this:

{code:java}
    private MBeanServerConnection getMBeanServerConnection() throws IOException {
        final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
        connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address));
        return connector.getMBeanServerConnection();

    }
{code}

To:

{code:java}

    private MBeanServerConnection getMBeanServerConnection() throws IOException {
        HashMap<String, String[]> propEnv = new HashMap<String, String[]>();
        String[] credentials = {  System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") };
        propEnv.put(JMXConnector.CREDENTIALS, credentials);
        final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
        connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv);
        return connector.getMBeanServerConnection();
    }
{code}


Could these kind of authentication being configurable?
It is important to us because this allows the tests to be executed against the docker images running in openshift.



> Make the authentication configurable in the eap testsuite 
> ----------------------------------------------------------
>
>                 Key: WFLY-7309
>                 URL: https://issues.jboss.org/browse/WFLY-7309
>             Project: WildFly
>          Issue Type: Bug
>          Components: Test Suite
>            Reporter: Filippe Spolti
>            Assignee: Filippe Spolti
>            Priority: Optional
>
> Actually some tests cases fails when running against a remote eap instance. 
> In this specific case instances running on Openshift v3.
> In order to get those tests working we have to modify some classes to configure the authentication.
> Example: 
> org.jboss.as.test.integration.ee.jmx.property.JMXPropertyEditorsTestCase, had to change this:
> {code:java}
>     private MBeanServerConnection getMBeanServerConnection() throws IOException {
>         final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
>         connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address));
>         return connector.getMBeanServerConnection();
>     }
> {code}
> To:
> {code:java}
>     private MBeanServerConnection getMBeanServerConnection() throws IOException {
>         HashMap<String, String[]> propEnv = new HashMap<String, String[]>();
>         String[] credentials = {  System.getProperty("jboss.management.user",""), System.getProperty("jboss.management.password","") };
>         propEnv.put(JMXConnector.CREDENTIALS, credentials);
>         final String address = managementClient.getMgmtAddress()+":"+managementClient.getMgmtPort();
>         connector = JMXConnectorFactory.connect(new JMXServiceURL("service:jmx:http-remoting-jmx://"+address),propEnv);
>         return connector.getMBeanServerConnection();
>     }
> {code}
> Could these kind of authentication being configurable?
> It is important to us because this allows the tests to be executed against the docker images running in openshift.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)