June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3373) Remove org.eclipse.jst.server.generic.jonas plugin from JBDS

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3373?page=com.atlassian.jira.plugin.... ] Fred Bricon reassigned JBDS-3373: --------------------------------- Assignee: Nick Boldt (was: Fred Bricon) > Remove org.eclipse.jst.server.generic.jonas plugin from JBDS > ------------------------------------------------------------ > > Key: JBDS-3373 > URL: https://issues.jboss.org/browse/JBDS-3373 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: updatesite > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Nick Boldt > Priority: Optional > Fix For: 9.0.0.Beta1 > > > com.jboss.devstudio.core.feature/feature.xml declares > {quote} > <import plugin="org.eclipse.jst.server.generic.jonas"/> > {quote} > I can't see *any* reason why we'd do that in 2015. > [~burrsutter], [~ldimaggio], [~maxandersen] : is there any client requirement about JOnAS support? > [~rob.stryker] does WTP require that plugin in any way? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19594) SSL callback: provide meaningful hostname verifier, stop always accepting hostnames

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19594?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19594: ------------------------------------------ We went out of time for this in 4.3.0.Beta1. Postponing. > SSL callback: provide meaningful hostname verifier, stop always accepting hostnames > ----------------------------------------------------------------------------------- > > Key: JBIDE-19594 > URL: https://issues.jboss.org/browse/JBIDE-19594 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > > We're currently using an SSL callback that will allow users to get informed and act upon "faulty" certificates (ex. self-signed ones) and mismatches btw. the host we're talking to and the one that is referenced in the ssl certificate: > {code:title=com.openshift.client.IHttpClient.ISSLCertificateCallback} > public interface ISSLCertificateCallback { > public boolean allowCertificate(X509Certificate[] chain); > public boolean allowHostname(String hostname, SSLSession session); > } > {code} > The callback that we are using in JBT is presenting a dialog in case the jdk cannot verify the certificate (ex. self signed certificates) and allows the user to accept/deny it. > In case the jdk cannot verify the hostname (the host we're talking to is not matching the host that's referenced in the certificate) we're currently always accepting the hostname: > {code:title=org.jboss.tools.openshift.express.internal.ui.wizard.connection.SSLCertificateCallback} > @Override > public boolean allowHostname(String hostname, SSLSession sslSession) { > return true; > } > {code} > We should find a meaningfull implementation of such a verification that does not simply always accept it. A first idea would be to present the mismatch to the user and allow it to accept/refute it. > This issue came up JBIDE-19581 when there was no callback installed which made the hostname verification fail as in jdk. When fetching the quickstarts OSJC is reaching out to https://hub.openshift.com (https://hub.openshift.com/api/v1/quickstarts/promoted.json) while the ssl certificate presented only covers openshift.redhat.com: > {code} > * Server certificate: > * subject: CN=openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US > * start date: Jul 23 00:00:00 2014 GMT > * expire date: Jul 27 12:00:00 2017 GMT > * common name: openshift.redhat.com > * issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3373) Remove org.eclipse.jst.server.generic.jonas plugin from JBDS

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3373?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3373: ----------------------------------- I'm not alone : https://dev.eclipse.org/mhonarc/lists/wtp-dev/msg09268.html [~nickboldt] : !https://crossfitaviano.files.wordpress.com/2015/02/lets-do-this-meme-no-cuss-words.jpg! > Remove org.eclipse.jst.server.generic.jonas plugin from JBDS > ------------------------------------------------------------ > > Key: JBDS-3373 > URL: https://issues.jboss.org/browse/JBDS-3373 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: updatesite > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Optional > Fix For: 9.0.0.Beta1 > > > com.jboss.devstudio.core.feature/feature.xml declares > {quote} > <import plugin="org.eclipse.jst.server.generic.jonas"/> > {quote} > I can't see *any* reason why we'd do that in 2015. > [~burrsutter], [~ldimaggio], [~maxandersen] : is there any client requirement about JOnAS support? > [~rob.stryker] does WTP require that plugin in any way? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19594) SSL callback: provide meaningful hostname verifier, stop always accepting hostnames

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19594?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19594: ------------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > SSL callback: provide meaningful hostname verifier, stop always accepting hostnames > ----------------------------------------------------------------------------------- > > Key: JBIDE-19594 > URL: https://issues.jboss.org/browse/JBIDE-19594 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > > We're currently using an SSL callback that will allow users to get informed and act upon "faulty" certificates (ex. self-signed ones) and mismatches btw. the host we're talking to and the one that is referenced in the ssl certificate: > {code:title=com.openshift.client.IHttpClient.ISSLCertificateCallback} > public interface ISSLCertificateCallback { > public boolean allowCertificate(X509Certificate[] chain); > public boolean allowHostname(String hostname, SSLSession session); > } > {code} > The callback that we are using in JBT is presenting a dialog in case the jdk cannot verify the certificate (ex. self signed certificates) and allows the user to accept/deny it. > In case the jdk cannot verify the hostname (the host we're talking to is not matching the host that's referenced in the certificate) we're currently always accepting the hostname: > {code:title=org.jboss.tools.openshift.express.internal.ui.wizard.connection.SSLCertificateCallback} > @Override > public boolean allowHostname(String hostname, SSLSession sslSession) { > return true; > } > {code} > We should find a meaningfull implementation of such a verification that does not simply always accept it. A first idea would be to present the mismatch to the user and allow it to accept/refute it. > This issue came up JBIDE-19581 when there was no callback installed which made the hostname verification fail as in jdk. When fetching the quickstarts OSJC is reaching out to https://hub.openshift.com (https://hub.openshift.com/api/v1/quickstarts/promoted.json) while the ssl certificate presented only covers openshift.redhat.com: > {code} > * Server certificate: > * subject: CN=openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US > * start date: Jul 23 00:00:00 2014 GMT > * expire date: Jul 27 12:00:00 2017 GMT > * common name: openshift.redhat.com > * issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3373) Remove org.eclipse.jst.server.generic.jonas plugin from JBDS

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3373?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3373: ------------------------------ CDW devel_ack: + (was: ?) Status: New (was: New) > Remove org.eclipse.jst.server.generic.jonas plugin from JBDS > ------------------------------------------------------------ > > Key: JBDS-3373 > URL: https://issues.jboss.org/browse/JBDS-3373 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: updatesite > Affects Versions: 9.0.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Optional > Fix For: 9.0.0.Beta1 > > > com.jboss.devstudio.core.feature/feature.xml declares > {quote} > <import plugin="org.eclipse.jst.server.generic.jonas"/> > {quote} > I can't see *any* reason why we'd do that in 2015. > [~burrsutter], [~ldimaggio], [~maxandersen] : is there any client requirement about JOnAS support? > [~rob.stryker] does WTP require that plugin in any way? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19095) OpenShift show all env. vars in Console view are listed as "Snapshot Restore/Deploy for application ..."

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19095?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19095: ------------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > OpenShift show all env. vars in Console view are listed as "Snapshot Restore/Deploy for application ..." > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19095 > URL: https://issues.jboss.org/browse/JBIDE-19095 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: environment_variables > Fix For: 4.3.0.Beta2 > > Attachments: erroneous-snapshot-restore-title.png > > > While having an application on OpenShift and listing all environment variable on it, there is incorrect label in ConsoleView. While choosing specific console, the listed environment variables for specific application are labeled there as "Snapshot Restore/Deploy for application ... (domainname):". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19095) OpenShift show all env. vars in Console view are listed as "Snapshot Restore/Deploy for application ..."

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19095?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19095: ------------------------------------------ We went out of time for this in 4.3.0.Beta1. Postponing. > OpenShift show all env. vars in Console view are listed as "Snapshot Restore/Deploy for application ..." > -------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19095 > URL: https://issues.jboss.org/browse/JBIDE-19095 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.2.Final > Reporter: Marián Labuda > Assignee: Andre Dietisheim > Priority: Minor > Labels: environment_variables > Fix For: 4.3.0.Beta2 > > Attachments: erroneous-snapshot-restore-title.png > > > While having an application on OpenShift and listing all environment variable on it, there is incorrect label in ConsoleView. While choosing specific console, the listed environment variables for specific application are labeled there as "Snapshot Restore/Deploy for application ... (domainname):". -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19506: ------------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Connection wizard: should have unit tests > ------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19506) Connection wizard: should have unit tests

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19506?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19506: ------------------------------------------ We went out of time for this in 4.3.0.Beta1. Postponing. > Connection wizard: should have unit tests > ------------------------------------------ > > Key: JBIDE-19506 > URL: https://issues.jboss.org/browse/JBIDE-19506 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta2 > > > In the new implementation of the connection wizard, that allows v2 and v3 connections (JBIDE-19096) we have rather complex behaviour that we should assert via unit tests. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19439) Explorer: Cannot delete v2 applications via "Del"-Key

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19439?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19439: ------------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Explorer: Cannot delete v2 applications via "Del"-Key > ----------------------------------------------------- > > Key: JBIDE-19439 > URL: https://issues.jboss.org/browse/JBIDE-19439 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.0.Alpha2 > Reporter: Andre Dietisheim > Priority: Minor > Fix For: 4.3.0.Beta2 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2015