-
Feature Request
-
Resolution: Done
-
Major
-
4.3.1.Beta1
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.
- blocks
-
JBIDE-20764 Create Server Adapter for OpenShift 3 applications
- Closed
-
JBIDE-21328 Create Server Adapter for OpenShift 3 applications
- Closed
- causes
-
JBIDE-21159 Cannot get SSL certificate
- Closed
-
JBIDE-21208 Cannot get SSL certificate
- Closed
-
JBIDE-21325 Connection wizard: trying to login with expired token causes 2nd, nested connection dialog
- Closed
-
JBIDE-21332 Connection wizard: trying to login with expired token causes 2nd, nested connection dialog
- Closed
-
JBIDE-21354 Connection wizard: trying to login with expired token causes 2nd, nested connection dialog
- Closed
- is related to
-
JBIDE-21155 fix test failures
- Closed
-
JBIDE-21156 Remove LazySSLCertificateCallback and LazyCredentialsPrompter
- Open