[JBoss JIRA] (JBIDE-24312) Explorer: SSL certificate dialog shows up many many times when using internal test server
by Mark Chappell (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24312?page=com.atlassian.jira.plugi... ]
Mark Chappell commented on JBIDE-24312:
---------------------------------------
Connecting using the openssl client I'm seeing a consistent Serial.
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1371 (0x55b)
Signature Algorithm: sha256WithRSAEncryption
Issuer: O=Red Hat, OU=prod, CN=Certificate Authority
Validity
Not Before: Oct 27 11:11:06 2016 GMT
Not After : Oct 27 11:11:06 2018 GMT
Subject: C=US, ST=North Carolina, L=Raleigh, O=Red Hat, Inc., OU=Information Technology, CN=open.paas.redhat.com
Could you grab the SSL cert (see also the internal chat that was started) and see if Java's actually parsing the certificate correctly?
> Explorer: SSL certificate dialog shows up many many times when using internal test server
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-24312
> URL: https://issues.jboss.org/browse/JBIDE-24312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Environment: MacOS
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.4.4.Final
>
> Attachments: Screencast_04-25-2017_06-56-06+PM.webm, create connection paas.mp4, diff-in-serial.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24312) Explorer: SSL certificate dialog shows up many many times when using internal test server
by Mark Chappell (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24312?page=com.atlassian.jira.plugi... ]
Mark Chappell edited comment on JBIDE-24312 at 4/26/17 6:24 AM:
----------------------------------------------------------------
Connecting using the openssl client I'm seeing a consistent Serial.
{{Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1371 (0x55b)
Signature Algorithm: sha256WithRSAEncryption
Issuer: O=Red Hat, OU=prod, CN=Certificate Authority
Validity
Not Before: Oct 27 11:11:06 2016 GMT
Not After : Oct 27 11:11:06 2018 GMT
Subject: C=US, ST=North Carolina, L=Raleigh, O=Red Hat, Inc., OU=Information Technology, CN=open.paas.redhat.com
}}
Could you grab the SSL cert (see also the internal chat that was started) and see if Java's actually parsing the certificate correctly?
was (Author: rhit_mchappell):
Connecting using the openssl client I'm seeing a consistent Serial.
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1371 (0x55b)
Signature Algorithm: sha256WithRSAEncryption
Issuer: O=Red Hat, OU=prod, CN=Certificate Authority
Validity
Not Before: Oct 27 11:11:06 2016 GMT
Not After : Oct 27 11:11:06 2018 GMT
Subject: C=US, ST=North Carolina, L=Raleigh, O=Red Hat, Inc., OU=Information Technology, CN=open.paas.redhat.com
Could you grab the SSL cert (see also the internal chat that was started) and see if Java's actually parsing the certificate correctly?
> Explorer: SSL certificate dialog shows up many many times when using internal test server
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-24312
> URL: https://issues.jboss.org/browse/JBIDE-24312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Environment: MacOS
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.4.4.Final
>
> Attachments: Screencast_04-25-2017_06-56-06+PM.webm, create connection paas.mp4, diff-in-serial.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24312) Explorer: SSL certificate dialog shows up many many times when using internal test server
by Mark Chappell (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24312?page=com.atlassian.jira.plugi... ]
Mark Chappell edited comment on JBIDE-24312 at 4/26/17 6:24 AM:
----------------------------------------------------------------
Connecting using the openssl client I'm seeing a consistent Serial.
{{
Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1371 (0x55b)
Signature Algorithm: sha256WithRSAEncryption
Issuer: O=Red Hat, OU=prod, CN=Certificate Authority
Validity
Not Before: Oct 27 11:11:06 2016 GMT
Not After : Oct 27 11:11:06 2018 GMT
Subject: C=US, ST=North Carolina, L=Raleigh, O=Red Hat, Inc., OU=Information Technology, CN=open.paas.redhat.com
}}
Could you grab the SSL cert (see also the internal chat that was started) and see if Java's actually parsing the certificate correctly?
was (Author: rhit_mchappell):
Connecting using the openssl client I'm seeing a consistent Serial.
{{Certificate:
Data:
Version: 3 (0x2)
Serial Number: 1371 (0x55b)
Signature Algorithm: sha256WithRSAEncryption
Issuer: O=Red Hat, OU=prod, CN=Certificate Authority
Validity
Not Before: Oct 27 11:11:06 2016 GMT
Not After : Oct 27 11:11:06 2018 GMT
Subject: C=US, ST=North Carolina, L=Raleigh, O=Red Hat, Inc., OU=Information Technology, CN=open.paas.redhat.com
}}
Could you grab the SSL cert (see also the internal chat that was started) and see if Java's actually parsing the certificate correctly?
> Explorer: SSL certificate dialog shows up many many times when using internal test server
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-24312
> URL: https://issues.jboss.org/browse/JBIDE-24312
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Environment: MacOS
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Fix For: 4.4.4.Final
>
> Attachments: Screencast_04-25-2017_06-56-06+PM.webm, create connection paas.mp4, diff-in-serial.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months
[JBoss JIRA] (JBIDE-24306) Cannot connect to JMX through OpenShift Server adapter to a FIS project
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24306?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-24306:
-------------------------------------
The host field was apparently disabled a year ago:
https://github.com/jbosstools/jbosstools-openshift/commit/5cfd773103264b8...
host for openshift 3 server adapter is defined by the selected route,
there is no sense in editing 'Host name' input. It should be disabled.
I'm not entirely sure if this is true though? Isn't a server adapter basically associated with one route and one hostname?
> Cannot connect to JMX through OpenShift Server adapter to a FIS project
> -----------------------------------------------------------------------
>
> Key: JBIDE-24306
> URL: https://issues.jboss.org/browse/JBIDE-24306
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM3
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Fix For: 4.4.4.Final
>
> Attachments: image-2017-04-25-14-48-51-427.png, screenshot-1.png
>
>
> !image-2017-04-25-14-48-51-427.png|thumbnail!
> in log:
> {noformat}
> eclipse.buildId=10.4.0.AM3-v20170406-1058-B390
> java.version=1.8.0_112
> java.vendor=Oracle Corporation
> BootLoader constants: OS=win32, ARCH=x86_64, WS=win32, NL=en_US
> Framework arguments: -product com.jboss.devstudio.core.product
> Command-line arguments: -data file:/C:/ws-devsuite-1.4.0-170425/ -os win32 -ws win32 -arch x86_64 -product com.jboss.devstudio.core.product
> org.jboss.tools.jmx.core
> Error
> Tue Apr 25 14:47:14 CEST 2017
> An error occurred while opening the connection.
> java.io.IOException: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:324)
> at org.jboss.tools.openshift.core.server.OpenshiftJMXConnectionProvider$1.verifyServerReachable(OpenshiftJMXConnectionProvider.java:80)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.connect(JolokiaConnectionWrapper.java:113)
> at org.jboss.tools.jmx.core.ConnectJob.run(ConnectJob.java:29)
> at org.jboss.tools.jmx.ui.internal.actions.DoubleClickAction$1.run(DoubleClickAction.java:71)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.jolokia.client.exception.J4pException: IO-Error while contacting the server: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.jolokia.client.J4pClient.mapException(J4pClient.java:333)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:198)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:168)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:117)
> at org.jboss.tools.jmx.jolokia.JolokiaConnectionWrapper.verifyServerReachable(JolokiaConnectionWrapper.java:311)
> ... 5 more
> Caused by: org.apache.http.client.ClientProtocolException: URI does not specify a valid host name: https:/api/v1/namespaces/test/pods/https:camel-ose-springboot-xml-1-oblwo:8778/proxy/jolokia/read/java.lang:type=Memory/HeapMemoryUsage
> at org.apache.http.impl.client.CloseableHttpClient.determineTarget(CloseableHttpClient.java:94)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:107)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:55)
> at org.jolokia.client.J4pClient.execute(J4pClient.java:190)
> ... 8 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 11 months