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

[Jeff Cantrill (JIRA)]

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

Jeff Cantrill commented on JBIDE-19096:
---------------------------------------

[~maxandersen] I would also prefer a more stylish and full-featured dialog, but I wouldn't allow that to hold up completion of this feature.  Maybe that can be an add-on or stretch goal for the June release.  I don't know how the rhc->osc is doing it now; I'm not sure it has been implemented yet since they have been focusing on getting certs to work.  It should be, however, landing shortly.  Isn't the token expiration whatever value that is designated by the OAuth provider?

> 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: fullauthoptions.bmml, fullauthoptions.png, 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)