[
https://issues.jboss.org/browse/JBIDE-21810?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-21810:
---------------------------------------
For some reason this did not work for me yesterday when I tried this on Windows -
[~jrichter1] installed the whole thing using the installer and then I started with a
running JBDS with CDK configured. It had a name like rhel-ose, so I'm pretty sure that
it was detected automatically.
When I started cdk (after changing the red hat account from jrichter to mmalina1, but this
shouldn't have any effect on the OpenShift connection, right?), I *think* I was shown
the certificate prompt right away but not sure. But what I'm sure of is that when I
tried to expand the OpenShift connection in OpenShift Explorer, I was shown the dialog and
had to enter credentials. I verified that the .cdk marker was there and contained both
login and password for openshift.
We will try this again today when a new build of the installer is ready.
For now I checked this on OS X where I detected the cdk setup from openshift-vagrant repo
which includes the .cdk marker file with everything and it worked fine - I didn't have
to enter credentials for openshift.
Respect .cdk password
---------------------
Key: JBIDE-21810
URL:
https://issues.jboss.org/browse/JBIDE-21810
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: cdk
Affects Versions: 4.3.1.Beta2
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.3.1.CR1, 4.4.0.Alpha1
Respect the values in .cdk for password, and change default username/pass to
openshift-dev/devel
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)