[jbosstools-issues] [JBoss JIRA] (JBIDE-19096) Connection wizard: Allow v2 and v3 Connections
Andre Dietisheim (JIRA)
issues at jboss.org
Mon Feb 2 05:20:49 EST 2015
[ https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13036719#comment-13036719 ]
Andre Dietisheim commented on JBIDE-19096:
------------------------------------------
We still need the basic infrastructure for this (basic connection wizard in common, extensions in v2 and v3 ui). In a first step we should have username/pw for v2 and the suggested, raw pasting approach for v3.
> 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)
More information about the jbosstools-issues
mailing list