-
Feature Request
-
Resolution: Done
-
Major
-
4.3.0.Alpha1
the existing UI for v2 OpenShift:
- new connection:
- existing connection:
In order to allow us to present v2 and v3 connections we have to change the connection wizard:
When creating a new connection, we only know whether a server is a v2 or v3 OpenShift host once, we have the url for it. The required settings that the user then has to provide then are different:
- v2 connections currently use username/password (and will most likely also allow x509, kerberos)
- v3 connections will most likely require OAuth settings.
- blocks
-
JBIDE-18999 As a user I want to connect to a v3 OpenShift instance
- Closed
- causes
-
JBIDE-19440 Explorer: connection is not refreshed after it was edited
- Closed
-
JBIDE-19456 Application wizard: The details section does not update/show the details for the selected application template
- Closed
-
JBIDE-19439 Explorer: Cannot delete v2 applications via "Del"-Key
- Closed
-
JBIDE-19506 Connection wizard, Connection: should have unit tests
- Pull Request Sent
- is related to
-
JBDS-3089 x509 Authentication to OpenShift
- Closed
-
JBIDE-20829 Support of krb5-principal keys in openshift
- Closed
-
JBIDE-19786 Connection wizard: cannot connect to console.stg.openshift.com
- Closed
-
JBIDE-19351 Connection wizard: V2 connections are not stored
- Closed
-
JBIDE-19353 Reenable tests for v2 Connection
- Closed
-
JBIDE-19433 Cant edit username and password for a connection
- Closed
-
JBIDE-19437 Connection wizard: v2 passwords are not stored
- Closed
-
JBIDE-19455 Connection wizard: if only v3 plugins installed, server type, url and "use default server" are predefined erroneously
- Closed
-
JBIDE-19442 Connection wizard:when providing the server, I dont want to have to provide a protocol (hostname should be sufficient)
- Closed
-
JBIDE-19444 Conncetion wizard: should not have to test v2 and v3 connections, only <automatic> ones
- Closed
-
JBIDE-19445 Connection wizard: Should have automcomplete/history for the server url
- Closed