[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:50 PM:
----------------------------------------------------------
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._
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
13 years
[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:49 PM:
----------------------------------------------------------
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._
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
13 years
[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:48 PM:
----------------------------------------------------------
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.
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}})
> 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
13 years
[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:47 PM:
----------------------------------------------------------
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}})
was (Author: brevilo):
In case you run into the following SSL-related exceptions:
* {{PKIX path building failed: 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}})
> 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
13 years
[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 commented on ARQ-1370:
----------------------------------
In case you run into the following SSL-related exceptions:
* {{PKIX path building failed: 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}})
> 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
13 years
[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 commented on ARQ-1370:
----------------------------------
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
13 years
[JBoss JIRA] (ARQ-1365) Warp: CommandEventBus doesn't support (port) redirects
by Oliver Bock (JIRA)
[ https://issues.jboss.org/browse/ARQ-1365?page=com.atlassian.jira.plugin.s... ]
Oliver Bock edited comment on ARQ-1365 at 4/5/13 3:01 AM:
----------------------------------------------------------
Sure, will do. It's basically just the above but I'll also add some details about web.xml and the required keystore.
was (Author: brevilo):
Sure, will do. It's basically just the above but I'll also add some details about web.xml and the required keystone.
> Warp: CommandEventBus doesn't support (port) redirects
> ------------------------------------------------------
>
> Key: ARQ-1365
> URL: https://issues.jboss.org/browse/ARQ-1365
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Beta1
> Reporter: Oliver Bock
> Assignee: Aris Tzoumas
> Labels: redirect, ssl, warp
> Fix For: warp_1.0.0.Alpha3
>
> Attachments: ARQ-1365_1.txt
>
>
> When JBosss AS 7 is configured to redirect HTTP (port 8888) to HTTPS (8889) in standalone.xml (web subsystem) using:
> {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_password_here]" session-timeout="900"/>
> </connector>
> {noformat}
> All Warp tests (client- and server-side) fail like this when using 1.0.0.Beta1-SNAPSHOT (client-side tests do work with 1.0.0.Alpha2):
> {noformat}
> java.lang.IllegalStateException: Error launching test at http://0.0.0.0:8888/test/CommandEventBus?className=TestClass&methodName=t.... Got 302 (Moved Temporarily)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.execute(CommandEventBus.java:266)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.access$100(CommandEventBus.java:67)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus$2.run(CommandEventBus.java:147)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> or
> java.lang.IllegalStateException: Error launching test at http://0.0.0.0:8888/test/CommandEventBus?className=TestClass&methodName=t.... Got 302 (Moved Temporarily)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.execute(CommandEventBus.java:266)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.executeCommandRemotely(CommandEventBus.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.warp.impl.client.eventbus.RemoteSuiteLifecyclePropagation.sendBefore(RemoteSuiteLifecyclePropagation.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> {noformat}
--
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
13 years
[JBoss JIRA] (ARQ-1365) Warp: CommandEventBus doesn't support (port) redirects
by Oliver Bock (JIRA)
[ https://issues.jboss.org/browse/ARQ-1365?page=com.atlassian.jira.plugin.s... ]
Oliver Bock commented on ARQ-1365:
----------------------------------
Sure, will do. It's basically just the above but I'll also add some details about web.xml and the required keystone.
> Warp: CommandEventBus doesn't support (port) redirects
> ------------------------------------------------------
>
> Key: ARQ-1365
> URL: https://issues.jboss.org/browse/ARQ-1365
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Beta1
> Reporter: Oliver Bock
> Assignee: Aris Tzoumas
> Labels: redirect, ssl, warp
> Fix For: warp_1.0.0.Alpha3
>
> Attachments: ARQ-1365_1.txt
>
>
> When JBosss AS 7 is configured to redirect HTTP (port 8888) to HTTPS (8889) in standalone.xml (web subsystem) using:
> {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_password_here]" session-timeout="900"/>
> </connector>
> {noformat}
> All Warp tests (client- and server-side) fail like this when using 1.0.0.Beta1-SNAPSHOT (client-side tests do work with 1.0.0.Alpha2):
> {noformat}
> java.lang.IllegalStateException: Error launching test at http://0.0.0.0:8888/test/CommandEventBus?className=TestClass&methodName=t.... Got 302 (Moved Temporarily)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.execute(CommandEventBus.java:266)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.access$100(CommandEventBus.java:67)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus$2.run(CommandEventBus.java:147)
> at java.util.TimerThread.mainLoop(Timer.java:555)
> at java.util.TimerThread.run(Timer.java:505)
> or
> java.lang.IllegalStateException: Error launching test at http://0.0.0.0:8888/test/CommandEventBus?className=TestClass&methodName=t.... Got 302 (Moved Temporarily)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.execute(CommandEventBus.java:266)
> at org.jboss.arquillian.warp.impl.client.eventbus.CommandEventBus.executeCommandRemotely(CommandEventBus.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.jboss.arquillian.core.impl.ObserverImpl.invoke(ObserverImpl.java:94)
> at org.jboss.arquillian.core.impl.EventContextImpl.invokeObservers(EventContextImpl.java:99)
> at org.jboss.arquillian.core.impl.EventContextImpl.proceed(EventContextImpl.java:81)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:135)
> at org.jboss.arquillian.core.impl.ManagerImpl.fire(ManagerImpl.java:115)
> at org.jboss.arquillian.core.impl.EventImpl.fire(EventImpl.java:67)
> at org.jboss.arquillian.warp.impl.client.eventbus.RemoteSuiteLifecyclePropagation.sendBefore(RemoteSuiteLifecyclePropagation.java:51)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> {noformat}
--
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
13 years