[
https://issues.jboss.org/browse/JBIDE-19096?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-19096:
---------------------------------------------
"but I wouldn't allow that to hold up completion of this feature." - i'm
not sure what "this feature" is if its not to handle different types of logins
?
if OSv3 still just support username/password then I agree we are fine and can move forward
on that just fine, but dont see what is missing ?
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)