[JBoss JIRA] (WFLY-7309) Make the authentication configurable in the eap testsuite
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFLY-7309?page=com.atlassian.jira.plugin.... ]
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)
9 years, 2 months
[JBoss JIRA] (WFLY-7312) wildfly parent specifies *.jbossorg-1 dependency which is not present in maven central
by Josef Ludvicek (JIRA)
[ https://issues.jboss.org/browse/WFLY-7312?page=com.atlassian.jira.plugin.... ]
Josef Ludvicek updated WFLY-7312:
---------------------------------
Description:
{{wildfly-parent}} BOM is present in maven central,
but itt's {{dependenciesManagement}} section specifies certain dependencies, which were not published to central and hence breaking the build.
For example
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>org.jboss.fuse.qa</groupId>
<artifactId>slf4j-reproducer</artifactId>
<version>0.0.1-SNAPSHOT</version>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-parent</artifactId>
<version>10.1.0.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>org.arquillian.cube</groupId>
<artifactId>arquillian-cube-docker</artifactId>
<version>1.0.0.Alpha15</version>
<scope>test</scope>
</dependency>
</dependencies>
</project>
{code}
fails:
{code}
[ERROR] Failed to execute goal on project slf4j-reproducer:
Could not resolve dependencies for project org.jboss.fuse.qa:slf4j-reproducer:jar:0.0.1-SNAPSHOT:
The following artifacts could not be resolved: org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1, org.slf4j:jcl-over-slf4j:jar:1.7.7.jbossorg-1:
Could not find artifact org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1 in central (https://repo.maven.apache.org/maven2) -> [Help 1]
[ERROR]
{code}
There is workaround - add jboss repository https://repository.jboss.org/nexus/content/groups/public/.
Shouldn't we publish all required artifacts to central to avoid similar problems in future ?
was:
{{wildfly-parent}} BOM is present in maven central,
but it specifies certain dependencies, which were not published to central and hence breaking the build.
For example
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>org.jboss.fuse.qa</groupId>
<artifactId>slf4j-reproducer</artifactId>
<version>0.0.1-SNAPSHOT</version>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-parent</artifactId>
<version>10.1.0.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>org.arquillian.cube</groupId>
<artifactId>arquillian-cube-docker</artifactId>
<version>1.0.0.Alpha15</version>
<scope>test</scope>
</dependency>
</dependencies>
</project>
{code}
fails:
{code}
[ERROR] Failed to execute goal on project slf4j-reproducer:
Could not resolve dependencies for project org.jboss.fuse.qa:slf4j-reproducer:jar:0.0.1-SNAPSHOT:
The following artifacts could not be resolved: org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1, org.slf4j:jcl-over-slf4j:jar:1.7.7.jbossorg-1:
Could not find artifact org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1 in central (https://repo.maven.apache.org/maven2) -> [Help 1]
[ERROR]
{code}
There is workaround - add jboss repository https://repository.jboss.org/nexus/content/groups/public/.
Shouldn't we publish all required artifacts to central to avoid similar problems in future ?
> wildfly parent specifies *.jbossorg-1 dependency which is not present in maven central
> --------------------------------------------------------------------------------------
>
> Key: WFLY-7312
> URL: https://issues.jboss.org/browse/WFLY-7312
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Reporter: Josef Ludvicek
> Assignee: Jason Greene
>
> {{wildfly-parent}} BOM is present in maven central,
> but itt's {{dependenciesManagement}} section specifies certain dependencies, which were not published to central and hence breaking the build.
> For example
> {code:xml}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>org.jboss.fuse.qa</groupId>
> <artifactId>slf4j-reproducer</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.wildfly</groupId>
> <artifactId>wildfly-parent</artifactId>
> <version>10.1.0.Final</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> </dependencies>
> </dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.arquillian.cube</groupId>
> <artifactId>arquillian-cube-docker</artifactId>
> <version>1.0.0.Alpha15</version>
> <scope>test</scope>
> </dependency>
> </dependencies>
> </project>
> {code}
> fails:
> {code}
> [ERROR] Failed to execute goal on project slf4j-reproducer:
> Could not resolve dependencies for project org.jboss.fuse.qa:slf4j-reproducer:jar:0.0.1-SNAPSHOT:
> The following artifacts could not be resolved: org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1, org.slf4j:jcl-over-slf4j:jar:1.7.7.jbossorg-1:
> Could not find artifact org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1 in central (https://repo.maven.apache.org/maven2) -> [Help 1]
> [ERROR]
> {code}
> There is workaround - add jboss repository https://repository.jboss.org/nexus/content/groups/public/.
> Shouldn't we publish all required artifacts to central to avoid similar problems in future ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7312) wildfly parent specifies *.jbossorg-1 dependency which is not present in maven central
by Josef Ludvicek (JIRA)
Josef Ludvicek created WFLY-7312:
------------------------------------
Summary: wildfly parent specifies *.jbossorg-1 dependency which is not present in maven central
Key: WFLY-7312
URL: https://issues.jboss.org/browse/WFLY-7312
Project: WildFly
Issue Type: Bug
Reporter: Josef Ludvicek
Assignee: Jason Greene
{{wildfly-parent}} BOM is present in maven central,
but it specifies certain dependencies, which were not published to central and hence breaking the build.
For example
{code:xml}
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>org.jboss.fuse.qa</groupId>
<artifactId>slf4j-reproducer</artifactId>
<version>0.0.1-SNAPSHOT</version>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.wildfly</groupId>
<artifactId>wildfly-parent</artifactId>
<version>10.1.0.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>org.arquillian.cube</groupId>
<artifactId>arquillian-cube-docker</artifactId>
<version>1.0.0.Alpha15</version>
<scope>test</scope>
</dependency>
</dependencies>
</project>
{code}
fails:
{code}
[ERROR] Failed to execute goal on project slf4j-reproducer:
Could not resolve dependencies for project org.jboss.fuse.qa:slf4j-reproducer:jar:0.0.1-SNAPSHOT:
The following artifacts could not be resolved: org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1, org.slf4j:jcl-over-slf4j:jar:1.7.7.jbossorg-1:
Could not find artifact org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1 in central (https://repo.maven.apache.org/maven2) -> [Help 1]
[ERROR]
{code}
There is workaround - add jboss repository https://repository.jboss.org/nexus/content/groups/public/.
Shouldn't we publish all required artifacts to central to avoid similar problems in future ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7312) wildfly parent specifies *.jbossorg-1 dependency which is not present in maven central
by Josef Ludvicek (JIRA)
[ https://issues.jboss.org/browse/WFLY-7312?page=com.atlassian.jira.plugin.... ]
Josef Ludvicek updated WFLY-7312:
---------------------------------
Affects Version/s: 10.1.0.Final
> wildfly parent specifies *.jbossorg-1 dependency which is not present in maven central
> --------------------------------------------------------------------------------------
>
> Key: WFLY-7312
> URL: https://issues.jboss.org/browse/WFLY-7312
> Project: WildFly
> Issue Type: Bug
> Affects Versions: 10.1.0.Final
> Reporter: Josef Ludvicek
> Assignee: Jason Greene
>
> {{wildfly-parent}} BOM is present in maven central,
> but it specifies certain dependencies, which were not published to central and hence breaking the build.
> For example
> {code:xml}
> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
> <modelVersion>4.0.0</modelVersion>
> <groupId>org.jboss.fuse.qa</groupId>
> <artifactId>slf4j-reproducer</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.wildfly</groupId>
> <artifactId>wildfly-parent</artifactId>
> <version>10.1.0.Final</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> </dependencies>
> </dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.arquillian.cube</groupId>
> <artifactId>arquillian-cube-docker</artifactId>
> <version>1.0.0.Alpha15</version>
> <scope>test</scope>
> </dependency>
> </dependencies>
> </project>
> {code}
> fails:
> {code}
> [ERROR] Failed to execute goal on project slf4j-reproducer:
> Could not resolve dependencies for project org.jboss.fuse.qa:slf4j-reproducer:jar:0.0.1-SNAPSHOT:
> The following artifacts could not be resolved: org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1, org.slf4j:jcl-over-slf4j:jar:1.7.7.jbossorg-1:
> Could not find artifact org.slf4j:slf4j-api:jar:1.7.7.jbossorg-1 in central (https://repo.maven.apache.org/maven2) -> [Help 1]
> [ERROR]
> {code}
> There is workaround - add jboss repository https://repository.jboss.org/nexus/content/groups/public/.
> Shouldn't we publish all required artifacts to central to avoid similar problems in future ?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7311) Make the authentication configurable in the eap testsuite
by Filippe Spolti (JIRA)
Filippe Spolti created WFLY-7311:
------------------------------------
Summary: Make the authentication configurable in the eap testsuite
Key: WFLY-7311
URL: https://issues.jboss.org/browse/WFLY-7311
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Filippe Spolti
Assignee: Filippe Spolti
Priority: Optional
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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7309) Make the authentication configurable in the eap testsuite
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFLY-7309?page=com.atlassian.jira.plugin.... ]
Filippe Spolti updated WFLY-7309:
---------------------------------
Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1384542
> 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 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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7310) Make the authentication configurable in the eap testsuite
by Filippe Spolti (JIRA)
Filippe Spolti created WFLY-7310:
------------------------------------
Summary: Make the authentication configurable in the eap testsuite
Key: WFLY-7310
URL: https://issues.jboss.org/browse/WFLY-7310
Project: WildFly
Issue Type: Bug
Components: Test Suite
Reporter: Filippe Spolti
Assignee: Filippe Spolti
Priority: Optional
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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7310) Make the authentication configurable in the eap testsuite
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFLY-7310?page=com.atlassian.jira.plugin.... ]
Filippe Spolti closed WFLY-7310.
--------------------------------
Resolution: Done
> Make the authentication configurable in the eap testsuite
> ----------------------------------------------------------
>
> Key: WFLY-7310
> URL: https://issues.jboss.org/browse/WFLY-7310
> Project: WildFly
> Issue Type: Bug
> Components: Test Suite
> Reporter: Filippe Spolti
> Assignee: Filippe Spolti
> Priority: Optional
>
> 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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7309) Make the authentication configurable in the eap testsuite
by Filippe Spolti (JIRA)
Filippe Spolti created WFLY-7309:
------------------------------------
Summary: 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
Priority: Optional
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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months
[JBoss JIRA] (WFLY-7309) Make the authentication configurable in the eap testsuite
by Filippe Spolti (JIRA)
[ https://issues.jboss.org/browse/WFLY-7309?page=com.atlassian.jira.plugin.... ]
Filippe Spolti reassigned WFLY-7309:
------------------------------------
Assignee: Filippe Spolti
> 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 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.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 2 months