[JBoss JIRA] (JBIDE-21159) Cannot get SSL certificate
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21159?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21159 at 12/2/15 5:01 AM:
-------------------------------------------------------------------
[~mlabuda] latest nightly was not correctly built. I retriggered jenkins and with this max reported that the issue went away, some weird issues persist though:
{quote}
Max Rydahl Andersen
10:56 AM
@AndreDietisheim after updating I seem to be able to login
seeing weird issues thouhg.
asked two-three times for login
print of "unauthorized. Trying to reauthenticate" in logs
Andre Dietisheim
10:56 AM
{quote}
{quote}
Andre Dietisheim
10:56 AM
@maxandersen ok, cool, happy if this fix works then
hmm
in sequence right 1 after the other?
{quote}
{quote}
Max Rydahl Andersen
10:57 AM
@AndreDietisheim yes.
{quote}
was (Author: adietish):
[~mlabuda] latest nightly was not correctly built. I retriggered jenkins and with this max reported that the issue went away, some weird issues persist though:
{quote}
Max Rydahl Andersen
10:56 AM
@AndreDietisheim after updating I seem to be able to login
seeing weird issues thouhg.
asked two-three times for login
print of "unauthorized. Trying to reauthenticate" in logs
Andre Dietisheim
10:56 AM
{quote}
Andre Dietisheim
10:56 AM
@maxandersen ok, cool, happy if this fix works then
hmm
in sequence right 1 after the other?
{quote}
{quote}
Max Rydahl Andersen
10:57 AM
@AndreDietisheim yes.
{quote}
> Cannot get SSL certificate
> --------------------------
>
> Key: JBIDE-21159
> URL: https://issues.jboss.org/browse/JBIDE-21159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Environment: openshift 3 tools 3.1.0.Beta1-v20151201-0140-B94
> Reporter: Jan Richter
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: connection, openshift_v3
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> When trying to log into internal OSE instance, I can't retrieve certificate from the server, therefore it is not possible to establish a new connection. Internal OSE instance also requires to use parameter "--insecure-skip-tls-verify=true" while logging in from 'oc' binary because of some x509 obscurities.
> Stacktrace:
> {noformat}
> com.openshift.restclient.OpenShiftException: javax.net.ssl.SSLHandshakeException while trying to get an authorization context for server https://console.engint.openshift.com
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:141)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getAuthorizationDetails(AuthorizationClient.java:78)
> at com.openshift.internal.restclient.DefaultClient.getAuthorizationDetails(DefaultClient.java:496)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.OAuthDetailView$AuthDetailsJob.run(OAuthDetailView.java:285)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No X509TrustManager implementation available
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1509)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)
> at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> ... 4 more
> Caused by: java.security.cert.CertificateException: No X509TrustManager implementation available
> at sun.security.ssl.DummyX509TrustManager.checkServerTrusted(SSLContextImpl.java:1119)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491)
> ... 24 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21159) Cannot get SSL certificate
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21159?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-21159 at 12/2/15 5:01 AM:
-------------------------------------------------------------------
[~mlabuda] latest nightly was not correctly built. I retriggered jenkins and with this max reported that the issue went away, some weird issues persist though:
{quote}
Max Rydahl Andersen
10:56 AM
@AndreDietisheim after updating I seem to be able to login
seeing weird issues thouhg.
asked two-three times for login
print of "unauthorized. Trying to reauthenticate" in logs
Andre Dietisheim
10:56 AM
{quote}
Andre Dietisheim
10:56 AM
@maxandersen ok, cool, happy if this fix works then
hmm
in sequence right 1 after the other?
{quote}
{quote}
Max Rydahl Andersen
10:57 AM
@AndreDietisheim yes.
{quote}
was (Author: adietish):
[~mlabuda] latest nightly was not correctly built. I retriggered jenkins and with this max reported that the issue went away, some weird issues persist though:
{quote}
Max Rydahl Andersen
10:56 AM
@AndreDietisheim after updating I seem to be able to login
seeing weird issues thouhg.
asked two-three times for login
print of "unauthorized. Trying to reauthenticate" in logs
Andre Dietisheim
10:56 AM
@maxandersen ok, cool, happy if this fix works then
hmm
in sequence right 1 after the other?
trying to reproduce...
{quote}
> Cannot get SSL certificate
> --------------------------
>
> Key: JBIDE-21159
> URL: https://issues.jboss.org/browse/JBIDE-21159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Environment: openshift 3 tools 3.1.0.Beta1-v20151201-0140-B94
> Reporter: Jan Richter
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: connection, openshift_v3
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> When trying to log into internal OSE instance, I can't retrieve certificate from the server, therefore it is not possible to establish a new connection. Internal OSE instance also requires to use parameter "--insecure-skip-tls-verify=true" while logging in from 'oc' binary because of some x509 obscurities.
> Stacktrace:
> {noformat}
> com.openshift.restclient.OpenShiftException: javax.net.ssl.SSLHandshakeException while trying to get an authorization context for server https://console.engint.openshift.com
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:141)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getAuthorizationDetails(AuthorizationClient.java:78)
> at com.openshift.internal.restclient.DefaultClient.getAuthorizationDetails(DefaultClient.java:496)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.OAuthDetailView$AuthDetailsJob.run(OAuthDetailView.java:285)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No X509TrustManager implementation available
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1509)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)
> at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> ... 4 more
> Caused by: java.security.cert.CertificateException: No X509TrustManager implementation available
> at sun.security.ssl.DummyX509TrustManager.checkServerTrusted(SSLContextImpl.java:1119)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491)
> ... 24 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21159) Cannot get SSL certificate
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21159?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-21159:
------------------------------------------
[~mlabuda] latest nightly was not correctly built. I retriggered jenkins and with this max reported that the issue went away, some weird issues persist though:
{quote}
Max Rydahl Andersen
10:56 AM
@AndreDietisheim after updating I seem to be able to login
seeing weird issues thouhg.
asked two-three times for login
print of "unauthorized. Trying to reauthenticate" in logs
Andre Dietisheim
10:56 AM
@maxandersen ok, cool, happy if this fix works then
hmm
in sequence right 1 after the other?
trying to reproduce...
{quote}
> Cannot get SSL certificate
> --------------------------
>
> Key: JBIDE-21159
> URL: https://issues.jboss.org/browse/JBIDE-21159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Environment: openshift 3 tools 3.1.0.Beta1-v20151201-0140-B94
> Reporter: Jan Richter
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: connection, openshift_v3
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> When trying to log into internal OSE instance, I can't retrieve certificate from the server, therefore it is not possible to establish a new connection. Internal OSE instance also requires to use parameter "--insecure-skip-tls-verify=true" while logging in from 'oc' binary because of some x509 obscurities.
> Stacktrace:
> {noformat}
> com.openshift.restclient.OpenShiftException: javax.net.ssl.SSLHandshakeException while trying to get an authorization context for server https://console.engint.openshift.com
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:141)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getAuthorizationDetails(AuthorizationClient.java:78)
> at com.openshift.internal.restclient.DefaultClient.getAuthorizationDetails(DefaultClient.java:496)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.OAuthDetailView$AuthDetailsJob.run(OAuthDetailView.java:285)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No X509TrustManager implementation available
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1509)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)
> at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> ... 4 more
> Caused by: java.security.cert.CertificateException: No X509TrustManager implementation available
> at sun.security.ssl.DummyX509TrustManager.checkServerTrusted(SSLContextImpl.java:1119)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491)
> ... 24 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21153) Use extension in OpenShiftCoreUIIntegation
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21153?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-21153:
-------------------------------------
Fix Version/s: 4.4.0.Alpha1
(was: 4.4.x)
> Use extension in OpenShiftCoreUIIntegation
> ------------------------------------------
>
> Key: JBIDE-21153
> URL: https://issues.jboss.org/browse/JBIDE-21153
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> the Connection class resides in the openshift core plugin. It happens that connections need to pop up dialogs in order to ex. let the user confirm ssl signatures or provide a token/credentials. To allow class to do this we have the OpenShiftCoreUIntegration currently, which is initialized by the activator in org.jboss.tools.openshift.ui by injecting the dialogs into OpenShiftCoreUIIntegration. This works fine as long as some UI is started before the connection gets activated. When creating a server adapter this doesnt work any more. The openshift server adapter resides in org.jboss.tools.openshift.core only, there's no openshift UI involved. The connection is therefore not able to prompt the user for a new token etc.
> We therefore have to change the current injection based approach (ui injects dialogs into core) by a extension point that the core is querying as soon as it requires some UI.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21153) Use extension in OpenShiftCoreUIIntegation
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21153?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-21153.
------------------------------------
Resolution: Done
re-closing
> Use extension in OpenShiftCoreUIIntegation
> ------------------------------------------
>
> Key: JBIDE-21153
> URL: https://issues.jboss.org/browse/JBIDE-21153
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> the Connection class resides in the openshift core plugin. It happens that connections need to pop up dialogs in order to ex. let the user confirm ssl signatures or provide a token/credentials. To allow class to do this we have the OpenShiftCoreUIntegration currently, which is initialized by the activator in org.jboss.tools.openshift.ui by injecting the dialogs into OpenShiftCoreUIIntegration. This works fine as long as some UI is started before the connection gets activated. When creating a server adapter this doesnt work any more. The openshift server adapter resides in org.jboss.tools.openshift.core only, there's no openshift UI involved. The connection is therefore not able to prompt the user for a new token etc.
> We therefore have to change the current injection based approach (ui injects dialogs into core) by a extension point that the core is querying as soon as it requires some UI.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21145) Component-install job does not reliably install all JBT IUs and so does not see changes between CI builds
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21145?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21145:
----------------------------------------
Thanks for clarifying that Pavol. So indeed, there is no need to trigger aggregation. So, assuming we can rely on the check of JBIDE-19670 to decide whether to publish or not, I believe we can simply get rid of the component-install job and have a scheduled build of aggregator (that would publish only when now content is available).
> Component-install job does not reliably install all JBT IUs and so does not see changes between CI builds
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21145
> URL: https://issues.jboss.org/browse/JBIDE-21145
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.1.Beta1, 4.4.0.Alpha1
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> We have often seen old artifacts on nightly sites (mars and neon too).
> It seems that the composite-install job [0], [1] is not reliable. So, the downstream JBT aggregate builds [2], [3] are not triggered automatically to pick up all new changes in the upstream JBT component site builds.
> [0] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-...
> [1] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite-...
> [2] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 6:15 AM NOT PUBLISHED: UNCHANGED")
> [3] http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-build-site... (latest build shows: "Nov 27, 2015 3:43 AM NOT PUBLISHED: UNCHANGED")
> Please investigate.
> Thanks!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21159) Cannot get SSL certificate
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21159?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21159:
---------------------------------------
Problem still persists with latest nightly where OpenShift plugin has timestamp v20151201-1936 build B97.
> Cannot get SSL certificate
> --------------------------
>
> Key: JBIDE-21159
> URL: https://issues.jboss.org/browse/JBIDE-21159
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Environment: openshift 3 tools 3.1.0.Beta1-v20151201-0140-B94
> Reporter: Jan Richter
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: connection, openshift_v3
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> When trying to log into internal OSE instance, I can't retrieve certificate from the server, therefore it is not possible to establish a new connection. Internal OSE instance also requires to use parameter "--insecure-skip-tls-verify=true" while logging in from 'oc' binary because of some x509 obscurities.
> Stacktrace:
> {noformat}
> com.openshift.restclient.OpenShiftException: javax.net.ssl.SSLHandshakeException while trying to get an authorization context for server https://console.engint.openshift.com
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:141)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getAuthorizationDetails(AuthorizationClient.java:78)
> at com.openshift.internal.restclient.DefaultClient.getAuthorizationDetails(DefaultClient.java:496)
> at org.jboss.tools.openshift.internal.ui.wizard.connection.OAuthDetailView$AuthDetailsJob.run(OAuthDetailView.java:285)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: No X509TrustManager implementation available
> at sun.security.ssl.Alerts.getSSLException(Alerts.java:192)
> at sun.security.ssl.SSLSocketImpl.fatal(SSLSocketImpl.java:1949)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:302)
> at sun.security.ssl.Handshaker.fatalSE(Handshaker.java:296)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1509)
> at sun.security.ssl.ClientHandshaker.processMessage(ClientHandshaker.java:216)
> at sun.security.ssl.Handshaker.processLoop(Handshaker.java:979)
> at sun.security.ssl.Handshaker.process_record(Handshaker.java:914)
> at sun.security.ssl.SSLSocketImpl.readRecord(SSLSocketImpl.java:1062)
> at sun.security.ssl.SSLSocketImpl.performInitialHandshake(SSLSocketImpl.java:1375)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1403)
> at sun.security.ssl.SSLSocketImpl.startHandshake(SSLSocketImpl.java:1387)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.createLayeredSocket(SSLConnectionSocketFactory.java:290)
> at org.apache.http.conn.ssl.SSLConnectionSocketFactory.connectSocket(SSLConnectionSocketFactory.java:259)
> at org.apache.http.impl.conn.HttpClientConnectionOperator.connect(HttpClientConnectionOperator.java:125)
> at org.apache.http.impl.conn.PoolingHttpClientConnectionManager.connect(PoolingHttpClientConnectionManager.java:319)
> at org.apache.http.impl.execchain.MainClientExec.establishRoute(MainClientExec.java:363)
> at org.apache.http.impl.execchain.MainClientExec.execute(MainClientExec.java:219)
> at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195)
> at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:86)
> at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108)
> at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:184)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:82)
> at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:106)
> at com.openshift.internal.restclient.authorization.AuthorizationClient.getContextUsingCredentials(AuthorizationClient.java:134)
> ... 4 more
> Caused by: java.security.cert.CertificateException: No X509TrustManager implementation available
> at sun.security.ssl.DummyX509TrustManager.checkServerTrusted(SSLContextImpl.java:1119)
> at sun.security.ssl.ClientHandshaker.serverCertificate(ClientHandshaker.java:1491)
> ... 24 more
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21165) Need to improve js tools (npm / bower) launch
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21165?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21165:
----------------------------------------
+1. Go ahead and reject JBIDE-21005
But let's handle correctly the situation when node/npm/etc are not installed/available. Not to just fail with error message but show some info/warning dialog to tell what we are missing and what the user should do.
> Need to improve js tools (npm / bower) launch
> ----------------------------------------------
>
> Key: JBIDE-21165
> URL: https://issues.jboss.org/browse/JBIDE-21165
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: nodejs
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Fix For: 4.4.0.Alpha1
>
>
> For now npm / bower is launched via node. Basically, this was done due to the fact that on Mac Os launched from desktop node PATH var not available:
> {quote}
> env: node: No such file or directory
> {quote}
> In order to handle it, it was suggested to launch npm / bower tools via node and have a preference for each tool. However, on thym project more elegant solution was found - execute the given command and returns a handle to the process.
> More details can be found here:
> - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core...
> - https://github.com/gorkem/thym/blob/use_cli/plugins/org.eclipse.thym.core...
> Basically, this approach kills two birds with one stone:
> 1. No mac os Path issue
> 2. No need to have preferences for node / npm / bower
> Also, it will be quite easy to provide cheatsheets for this tools which will include sets of commands
> The plan is:
> - reimplement the launch process that will be generic for both jsdt and thym (maybe some other tools in future)
> - remove irrelevant code with preferences, detectors etc
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months