[JBoss JIRA] (ARQ-1372) Document dependency set up for OSGi containers
by Thomas Diesler (JIRA)
[ https://issues.jboss.org/browse/ARQ-1372?page=com.atlassian.jira.plugin.s... ]
Thomas Diesler reassigned ARQ-1372:
-----------------------------------
Assignee: (was: Thomas Diesler)
The remote container for R5 is currently not maintained. We use the AS7 managed container for remote OSGi runtime testing.
Please reopen if you like to resurrect the remote container for other OSGi runtimes.
> Document dependency set up for OSGi containers
> ----------------------------------------------
>
> Key: ARQ-1372
> URL: https://issues.jboss.org/browse/ARQ-1372
> Project: Arquillian
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: OSGi Containers
> Reporter: Richard Vitek
>
> Copying my [question from Arquillian forum|https://community.jboss.org/message/806176#806176]:
> I just started with Arquillian as I like its idea and the way how its done but unfortunately I run into total lack of documentation for (remote) OSGI container. I've been trying to implement an integration test on real running OSGi framework (Equinox, in case it matters) but not much joy so far - I ran into JAR hell when trying to setup maven dependencies for OSGi remote container. I haven't found a single piece of docs or article anywhere on internet about this and lost almost on day on classpath setup issues .
> I use Maven (3.0.4) to get the setup done, followed the general instructions from the Getting started guide but didn't really get anywhere - all the time I've been getting ClassNotFound/MethodNotFound and other invalid-classpath-related exceptions. Please, somebody provide a working pom.xml and for Arquillian team - please document this somewhere as it is royal pain in the ass! This is how my pom.xml looks like:
> {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>com.orchestral.notification</groupId>
> <artifactId>notification.test.integration</artifactId>
> <version>0.0.1-SNAPSHOT</version>
> <name>Notifications Integration Tests</name>
> <properties>
> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
> </properties>
> <repositories>
> <repository>
> <id>jboss-public-repository-group</id>
> <name>JBoss Public Repository Group</name>
> <url>http://repository.jboss.org/nexus/content/groups/public/</url>
> </repository>
> <repository>
> <releases>
> <enabled>true</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> <id>jboss-central</id>
> <name>JBoss Central</name>
> <url>https://repository.jboss.org/nexus/content/repositories/central/</url>
> </repository>
> <repository>
> <releases>
> <enabled>true</enabled>
> </releases>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> <id>jboss-public</id>
> <name>JBoss Public</name>
> <url>https://repository.jboss.org/nexus/content/repositories/public-jboss/</url>
> </repository>
> </repositories>
> <dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.arquillian</groupId>
> <artifactId>arquillian-bom</artifactId>
> <version>1.0.3.Final</version>
> <scope>import</scope>
> <type>pom</type>
> </dependency>
> </dependencies>
> </dependencyManagement>
> <dependencies>
> <dependency>
> <groupId>org.jboss.arquillian.container</groupId>
> <artifactId>arquillian-container-osgi-remote</artifactId>
> <version>1.0.2.Final</version>
> </dependency>
> <dependency>
> <groupId>org.jboss.arquillian.junit</groupId>
> <artifactId>arquillian-junit-container</artifactId>
> <scope>test</scope>
> </dependency>
> <!-- <dependency> -->
> <!-- <groupId>org.jboss.osgi.bundles</groupId> -->
> <!-- <artifactId>jboss-osgi-jmx</artifactId> -->
> <!-- <version>1.0.3</version> -->
> <!-- </dependency> -->
> <dependency>
> <groupId>javax.inject</groupId>
> <artifactId>javax.inject</artifactId>
> <version>1</version>
> </dependency>
> <dependency>
> <groupId>junit</groupId>
> <artifactId>junit</artifactId>
> <version>4.8.1</version>
> <scope>test</scope>
> </dependency>
> </dependencies>
> <build>
> <plugins>
> <plugin>
> <artifactId>maven-compiler-plugin</artifactId>
> <version>2.3.2</version>
> <configuration>
> <source>1.7</source>
> <target>1.7</target>
> </configuration>
> </plugin>
> <plugin>
> <artifactId>maven-surefire-plugin</artifactId>
> <version>2.12</version>
> </plugin>
> </plugins>
> </build>
> </project>
> {code}
--
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
11 years, 9 months
[JBoss JIRA] (ARQ-1372) Document dependency set up for OSGi containers
by Richard Vitek (JIRA)
Richard Vitek created ARQ-1372:
----------------------------------
Summary: Document dependency set up for OSGi containers
Key: ARQ-1372
URL: https://issues.jboss.org/browse/ARQ-1372
Project: Arquillian
Issue Type: Task
Security Level: Public (Everyone can see)
Components: OSGi Containers
Reporter: Richard Vitek
Assignee: Thomas Diesler
Copying my [question from Arquillian forum|https://community.jboss.org/message/806176#806176]:
I just started with Arquillian as I like its idea and the way how its done but unfortunately I run into total lack of documentation for (remote) OSGI container. I've been trying to implement an integration test on real running OSGi framework (Equinox, in case it matters) but not much joy so far - I ran into JAR hell when trying to setup maven dependencies for OSGi remote container. I haven't found a single piece of docs or article anywhere on internet about this and lost almost on day on classpath setup issues .
I use Maven (3.0.4) to get the setup done, followed the general instructions from the Getting started guide but didn't really get anywhere - all the time I've been getting ClassNotFound/MethodNotFound and other invalid-classpath-related exceptions. Please, somebody provide a working pom.xml and for Arquillian team - please document this somewhere as it is royal pain in the ass! This is how my pom.xml looks like:
{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>com.orchestral.notification</groupId>
<artifactId>notification.test.integration</artifactId>
<version>0.0.1-SNAPSHOT</version>
<name>Notifications Integration Tests</name>
<properties>
<project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
</properties>
<repositories>
<repository>
<id>jboss-public-repository-group</id>
<name>JBoss Public Repository Group</name>
<url>http://repository.jboss.org/nexus/content/groups/public/</url>
</repository>
<repository>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
<id>jboss-central</id>
<name>JBoss Central</name>
<url>https://repository.jboss.org/nexus/content/repositories/central/</url>
</repository>
<repository>
<releases>
<enabled>true</enabled>
</releases>
<snapshots>
<enabled>true</enabled>
</snapshots>
<id>jboss-public</id>
<name>JBoss Public</name>
<url>https://repository.jboss.org/nexus/content/repositories/public-jboss/</url>
</repository>
</repositories>
<dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.arquillian</groupId>
<artifactId>arquillian-bom</artifactId>
<version>1.0.3.Final</version>
<scope>import</scope>
<type>pom</type>
</dependency>
</dependencies>
</dependencyManagement>
<dependencies>
<dependency>
<groupId>org.jboss.arquillian.container</groupId>
<artifactId>arquillian-container-osgi-remote</artifactId>
<version>1.0.2.Final</version>
</dependency>
<dependency>
<groupId>org.jboss.arquillian.junit</groupId>
<artifactId>arquillian-junit-container</artifactId>
<scope>test</scope>
</dependency>
<!-- <dependency> -->
<!-- <groupId>org.jboss.osgi.bundles</groupId> -->
<!-- <artifactId>jboss-osgi-jmx</artifactId> -->
<!-- <version>1.0.3</version> -->
<!-- </dependency> -->
<dependency>
<groupId>javax.inject</groupId>
<artifactId>javax.inject</artifactId>
<version>1</version>
</dependency>
<dependency>
<groupId>junit</groupId>
<artifactId>junit</artifactId>
<version>4.8.1</version>
<scope>test</scope>
</dependency>
</dependencies>
<build>
<plugins>
<plugin>
<artifactId>maven-compiler-plugin</artifactId>
<version>2.3.2</version>
<configuration>
<source>1.7</source>
<target>1.7</target>
</configuration>
</plugin>
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>2.12</version>
</plugin>
</plugins>
</build>
</project>
{code}
--
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
11 years, 9 months
[JBoss JIRA] (ARQGRA-238) Catch client-side errors
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQGRA-238?page=com.atlassian.jira.plugin... ]
Lukáš Fryč edited comment on ARQGRA-238 at 4/6/13 8:28 AM:
-----------------------------------------------------------
We can use proxy in the middle of the request which would inject the script on load - we can do the same for guards and other scripts:
* the proxy stuff is implemented in Warp
* the stream buffer used to change the HTML on the fly is implemented in URLRewriter (afaik)
was (Author: lfryc):
We can use proxy in the middle of the request which would inject the script on load - we can do the same for guards and other scripts.
> Catch client-side errors
> ------------------------
>
> Key: ARQGRA-238
> URL: https://issues.jboss.org/browse/ARQGRA-238
> Project: Arquillian Graphene
> Issue Type: Feature Request
> Affects Versions: 2.0.0.Alpha2
> Reporter: Lukáš Fryč
> Fix For: 2.0-Tracking
>
>
> Graphene should allow to inspect errors on client-side.
> E.g. console.log output.
--
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
11 years, 9 months
[JBoss JIRA] (ARQ-1370) Warp: support SSL for CommandService using untrusted communication
by Oliver Bock (JIRA)
[ https://issues.jboss.org/browse/ARQ-1370?page=com.atlassian.jira.plugin.s... ]
Oliver Bock edited comment on ARQ-1370 at 4/5/13 3:59 PM:
----------------------------------------------------------
Some workarounds in case you run into the following SSL-related exceptions:
* {{sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target}}
** add {{-Djavax.net.ssl.trustStore=/path/to/local/keystore}} (default: {{~/.keystore}}) to the client VM
* {{java.security.cert.CertificateException: No subject alternative names present}}
** recreate your keystore adding a SAN or Subject Alternative Name by adding this argument to keytool: {{\-ext san=ip:0.0.0.0}}\\(the IP can be found in {{standalone.xml}} at {{interfaces/interface[@name="public"]/inet-address}})
_Note: both exceptions should vanish as soon as this issue is resolved and the workarounds should become unnecessary._
was (Author: brevilo):
In case you run into the following SSL-related exceptions:
* {{sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target}}
** add {{-Djavax.net.ssl.trustStore=/path/to/local/keystore}} (default: {{~/.keystore}}) to the client VM
* {{java.security.cert.CertificateException: No subject alternative names present}}
** recreate your keystore adding a SAN or Subject Alternative Name by adding this argument to keytool: {{\-ext san=ip:0.0.0.0}}\\(the IP can be found in {{standalone.xml}} at {{interfaces/interface[@name="public"]/inet-address}})
_Note: both exceptions should vanish as soon as this issue is resolved._
> Warp: support SSL for CommandService using untrusted communication
> ------------------------------------------------------------------
>
> Key: ARQ-1370
> URL: https://issues.jboss.org/browse/ARQ-1370
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha3
> Reporter: Lukáš Fryč
>
> We can make use of HTTP client which will automatically trust SSL endpoint.
> http://stackoverflow.com/questions/2703161/how-to-ignore-ssl-certificate-...
--
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
11 years, 9 months
[JBoss JIRA] (ARQ-1370) Warp: support SSL for CommandService using untrusted communication
by Oliver Bock (JIRA)
[ https://issues.jboss.org/browse/ARQ-1370?page=com.atlassian.jira.plugin.s... ]
Oliver Bock edited comment on ARQ-1370 at 4/5/13 4:00 PM:
----------------------------------------------------------
Some workarounds in case you run into the following SSL-related exceptions:
* {{sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target}}
** add {{-Djavax.net.ssl.trustStore=/path/to/local/keystore}} (default: {{~/.keystore}}) to the client VM
* {{java.security.cert.CertificateException: No subject alternative names present}}
** recreate your keystore adding a Subject Alternative Name (SAN) by adding this argument to keytool: {{\-ext san=ip:0.0.0.0}}\\(the IP can be found in {{standalone.xml}} at {{interfaces/interface[@name="public"]/inet-address}})
_Note: both exceptions should vanish as soon as this issue is resolved and the workarounds should become unnecessary._
was (Author: brevilo):
Some workarounds in case you run into the following SSL-related exceptions:
* {{sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target}}
** add {{-Djavax.net.ssl.trustStore=/path/to/local/keystore}} (default: {{~/.keystore}}) to the client VM
* {{java.security.cert.CertificateException: No subject alternative names present}}
** recreate your keystore adding a SAN or Subject Alternative Name by adding this argument to keytool: {{\-ext san=ip:0.0.0.0}}\\(the IP can be found in {{standalone.xml}} at {{interfaces/interface[@name="public"]/inet-address}})
_Note: both exceptions should vanish as soon as this issue is resolved and the workarounds should become unnecessary._
> Warp: support SSL for CommandService using untrusted communication
> ------------------------------------------------------------------
>
> Key: ARQ-1370
> URL: https://issues.jboss.org/browse/ARQ-1370
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha3
> Reporter: Lukáš Fryč
>
> We can make use of HTTP client which will automatically trust SSL endpoint.
> http://stackoverflow.com/questions/2703161/how-to-ignore-ssl-certificate-...
--
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
11 years, 9 months
[JBoss JIRA] (ARQ-1370) Warp: support SSL for CommandService using untrusted communication
by Oliver Bock (JIRA)
[ https://issues.jboss.org/browse/ARQ-1370?page=com.atlassian.jira.plugin.s... ]
Oliver Bock edited comment on ARQ-1370 at 4/5/13 3:57 PM:
----------------------------------------------------------
Some setup hints for testing with JBoss AS 7...
# Create a self-signed certificate by creating a local keystore following the [JBossWeb SSL Configuration HOW-TO|http://docs.jboss.org/jbossweb/7.0.x/ssl-howto.html] ("Prepare the Certificate Keystore")
{noformat}
keytool -genkey -alias tomcat -keyalg RSA
{noformat}
# Enable socket binding for HTTPS ({{standalone.xml}} at {{socket-binding-group[@name="standard-sockets"]}}):
{noformat}
<socket-binding name="https" port="8889"/>
{noformat}
# Redirect HTTP to HTTPS ({{standalone.xml}} at {{profile/subsystem[@xmlns="urn:jboss:domain:web:1.1"]}}):
{noformat}
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" redirect-port="8889"/>
<connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
<ssl password="[your_keystore_password_here]" session-timeout="900"/>
</connector>
{noformat}
# Enable SSL for your web app ([web.xml|http://docs.oracle.com/javaee/6/tutorial/doc/gkbaa.html#bncbm]):
{noformat}
<security-constraint>
<web-resource-collection>
<web-resource-name>secure</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
{noformat}
was (Author: brevilo):
Some setup hints for testing with JBoss AS 7...
# Create a self-signed certificate by creating a local keystore following the [JBossWeb SSL Configuration HOW-TO|http://docs.jboss.org/jbossweb/7.0.x/ssl-howto.html] ("Prepare the Certificate Keystore")
{noformat}
keytool -genkey -alias tomcat -keyalg RSA
{noformat}
# Enable socket binding for HTTPS ({{standalone.xml}} at {{socket-binding-group[@name="standard-sockets"]}}):
{noformat}
<socket-binding name="https" port="8889"/>
{noformat}
# Redirect HTTP to HTTPS ({{standalone.xml}} at {{profile/subsystem[@xmlns="urn:jboss:domain:web:1.1"]}}):
{noformat}
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" redirect-port="8889"/>
<connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
<ssl password="[your_keystore_password_here]" session-timeout="900"/>
</connector>
{noformat}
# Enable SSL for your web app ([web.xml|http://docs.oracle.com/javaee/6/tutorial/doc/gkbaa.html#bncbm]):
{noformat}
<security-constraint>
<web-resource-collection>
<web-resource-name>secure</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
{noformat}
HTH
> Warp: support SSL for CommandService using untrusted communication
> ------------------------------------------------------------------
>
> Key: ARQ-1370
> URL: https://issues.jboss.org/browse/ARQ-1370
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha3
> Reporter: Lukáš Fryč
>
> We can make use of HTTP client which will automatically trust SSL endpoint.
> http://stackoverflow.com/questions/2703161/how-to-ignore-ssl-certificate-...
--
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
11 years, 9 months
[JBoss JIRA] (ARQ-1370) Warp: support SSL for CommandService using untrusted communication
by Oliver Bock (JIRA)
[ https://issues.jboss.org/browse/ARQ-1370?page=com.atlassian.jira.plugin.s... ]
Oliver Bock edited comment on ARQ-1370 at 4/5/13 3:56 PM:
----------------------------------------------------------
Some setup hints for testing with JBoss AS 7...
# Create a self-signed certificate by creating a local keystore following the [JBossWeb SSL Configuration HOW-TO|http://docs.jboss.org/jbossweb/7.0.x/ssl-howto.html] ("Prepare the Certificate Keystore")
{noformat}
keytool -genkey -alias tomcat -keyalg RSA
{noformat}
# Enable socket binding for HTTPS ({{standalone.xml}} at {{socket-binding-group[@name="standard-sockets"]}}):
{noformat}
<socket-binding name="https" port="8889"/>
{noformat}
# Redirect HTTP to HTTPS ({{standalone.xml}} at {{profile/subsystem[@xmlns="urn:jboss:domain:web:1.1"]}}):
{noformat}
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" redirect-port="8889"/>
<connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
<ssl password="[your_keystore_password_here]" session-timeout="900"/>
</connector>
{noformat}
# Enable SSL for your web app ([web.xml|http://docs.oracle.com/javaee/6/tutorial/doc/gkbaa.html#bncbm]):
{noformat}
<security-constraint>
<web-resource-collection>
<web-resource-name>secure</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
{noformat}
HTH
was (Author: brevilo):
Some setup hints for testing with JBoss AS 7...
# Create a self-signed certificate by creating a local keystore following the [JBossWeb SSL Configuration HOW-TO|http://docs.jboss.org/jbossweb/7.0.x/ssl-howto.html] ("Prepare the Certificate Keystore")
{noformat}
keytool -genkey -alias tomcat -keyalg RSA
{noformat}
# Enable socket binding for HTTPS ({{standalone.xml}} at {{socket-binding-group[@name="standard-sockets"]}}):
{noformat}
<socket-binding name="https" port="8889"/>
{noformat}
# Redirect HTTP to HTTPS (standalone.xml / web subsystem):
{noformat}
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" redirect-port="8889"/>
<connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
<ssl password="[your_keystore_password_here]" session-timeout="900"/>
</connector>
{noformat}
# Enable SSL for your web app ([web.xml|http://docs.oracle.com/javaee/6/tutorial/doc/gkbaa.html#bncbm]):
{noformat}
<security-constraint>
<web-resource-collection>
<web-resource-name>secure</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
{noformat}
HTH
> Warp: support SSL for CommandService using untrusted communication
> ------------------------------------------------------------------
>
> Key: ARQ-1370
> URL: https://issues.jboss.org/browse/ARQ-1370
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha3
> Reporter: Lukáš Fryč
>
> We can make use of HTTP client which will automatically trust SSL endpoint.
> http://stackoverflow.com/questions/2703161/how-to-ignore-ssl-certificate-...
--
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
11 years, 9 months
[JBoss JIRA] (ARQ-1370) Warp: support SSL for CommandService using untrusted communication
by Oliver Bock (JIRA)
[ https://issues.jboss.org/browse/ARQ-1370?page=com.atlassian.jira.plugin.s... ]
Oliver Bock edited comment on ARQ-1370 at 4/5/13 3:54 PM:
----------------------------------------------------------
Some setup hints for testing with JBoss AS 7...
# Create a self-signed certificate by creating a local keystore following the [JBossWeb SSL Configuration HOW-TO|http://docs.jboss.org/jbossweb/7.0.x/ssl-howto.html] ("Prepare the Certificate Keystore")
{noformat}
keytool -genkey -alias tomcat -keyalg RSA
{noformat}
# Enable socket binding for HTTPS ({{standalone.xml}} at {{socket-binding-group[@name="standard-sockets"]}}):
{noformat}
<socket-binding name="https" port="8889"/>
{noformat}
# Redirect HTTP to HTTPS (standalone.xml / web subsystem):
{noformat}
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" redirect-port="8889"/>
<connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
<ssl password="[your_keystore_password_here]" session-timeout="900"/>
</connector>
{noformat}
# Enable SSL for your web app ([web.xml|http://docs.oracle.com/javaee/6/tutorial/doc/gkbaa.html#bncbm]):
{noformat}
<security-constraint>
<web-resource-collection>
<web-resource-name>secure</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
{noformat}
HTH
was (Author: brevilo):
Some setup hints for testing with JBoss AS 7...
# Create a self-signed certificate by creating a local keystore following the [JBossWeb SSL Configuration HOW-TO|http://docs.jboss.org/jbossweb/7.0.x/ssl-howto.html] ("Prepare the Certificate Keystore")
{noformat}
keytool -genkey -alias tomcat -keyalg RSA
{noformat}
# Enable socket binding for HTTPS (standalone.xml / socket-binding-group "standard-sockets"):
{noformat}
<socket-binding name="https" port="8889"/>
{noformat}
# Redirect HTTP to HTTPS (standalone.xml / web subsystem):
{noformat}
<connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http" redirect-port="8889"/>
<connector name="https" protocol="HTTP/1.1" scheme="https" socket-binding="https" secure="true">
<ssl password="[your_keystore_password_here]" session-timeout="900"/>
</connector>
{noformat}
# Enable SSL for your web app ([web.xml|http://docs.oracle.com/javaee/6/tutorial/doc/gkbaa.html#bncbm]):
{noformat}
<security-constraint>
<web-resource-collection>
<web-resource-name>secure</web-resource-name>
<url-pattern>/*</url-pattern>
</web-resource-collection>
<user-data-constraint>
<transport-guarantee>CONFIDENTIAL</transport-guarantee>
</user-data-constraint>
</security-constraint>
{noformat}
HTH
> Warp: support SSL for CommandService using untrusted communication
> ------------------------------------------------------------------
>
> Key: ARQ-1370
> URL: https://issues.jboss.org/browse/ARQ-1370
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha3
> Reporter: Lukáš Fryč
>
> We can make use of HTTP client which will automatically trust SSL endpoint.
> http://stackoverflow.com/questions/2703161/how-to-ignore-ssl-certificate-...
--
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
11 years, 9 months