[
https://issues.jboss.org/browse/JBIDE-19829?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-19829:
---------------------------------------
[~adietish] [~maxandersen] Submitted this PR and tried against staging environment and
failed with:
{{ com.openshift.restclient.ResourceFactoryException: Unable to create v1beta1 resource
kind User}}
This is because we did not add the user kind for v1beta1. Staging environment is expected
to be updated sometime next week, but in the mean time, we can't connect. Given,
v1beta1 is to be dropped VERY soon, is there value in adding v1beta1 support for types
that are in v1beta3? For now I have not logged any issue to address this.
Add Oauth support to the Openshift Connection Wizard
----------------------------------------------------
Key: JBIDE-19829
URL:
https://issues.jboss.org/browse/JBIDE-19829
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.0.Beta2
Reporter: Jeff Cantrill
Assignee: Jeff Cantrill
Attachments: Proposed Connection Wizard Chages.png
Modify the connection wizard so the v3 server can auto-detect the auth type and support
OAuth
* Remove server type verify button
* Add v3 auth box (Auto/OAuth/Basic)
* Optional...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)