[jbosstools-issues] [JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections

[Max Rydahl Andersen (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13035529#comment-13035529 ] 

Max Rydahl Andersen commented on JBIDE-19096:
---------------------------------------------

"most likely require OAuth" - are we sure it wont also be needing to support various sign ins like v2 ? 

About UI this is unfortunately going to be a bit tricky, but if we need to support multiple auth mechanics anyways its needed.

We don't yet have a default openshift 3 server url, but how about we assume we will get one then instead of just having one default server checkbox we add the default servers to the combo and have it remember the last one used.

i.e. once we have a default online url there will be  "default OpenShift v2 server" and "default OpensShift v3 server"  entries into this dialog which will leave the host part empty in the preference to signal it should be calculated based on preferences + file info like ~/.openshift/express.conf (for v2)

Then the authentication part will also have to be extended to have a combo like:
Authentication method with a combo which would need to somehow be offering all the options and once verifcation is executed if the url is not supporting the auth method tell the user and disable the options that are not valid.

We can once the user starts entering credentials in the *background* ping the url to try detect auth methods and then filter/warn if the auth method is not supported but it has to be in the background (and cached) or on explicit verification to avoid a nasty slow dialog for entering credentials


> Connection wizard: Allow v2 and v3 Connections
> ----------------------------------------------
>
>                 Key: JBIDE-19096
>                 URL: https://issues.jboss.org/browse/JBIDE-19096
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: openshift
>    Affects Versions: 4.3.0.Alpha1
>            Reporter: Andre Dietisheim
>              Labels: connection_wizard
>             Fix For: 4.3.0.Alpha1
>
>         Attachments: screenshot-openshift-signin.png
>
>
> !screenshot-openshift-signin.png!
> 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. 



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)