[
https://issues.jboss.org/browse/JBIDE-13522?page=com.atlassian.jira.plugi...
]
RH Bugzilla Integration commented on JBIDE-13522:
-------------------------------------------------
Chandrika Gole <cgole(a)redhat.com> made a comment on [bug
910442|https://bugzilla.redhat.com/show_bug.cgi?id=910442]
verified this using rhc-1.4.8 on staging
Steps to reproduce -
1. On a system w/o express.conf installed rhc-1.4.8
2. Run rhc setup
3. Check the ~/openshift/express.conf.
========================================================================
# The OpenShift server to connect to
libra_server=openshift.redhat.com
# Your OpenShift login name
default_rhlogin=cgole(a)redhat.com
# The default timeout for network operations
#timeout=<integer>
# If true, certificate errors will be ignored.
# WARNING: This may allow others to eavesdrop on your communication with OpenShift.
#insecure=<boolean>
# The SSL protocol version to use when connecting to this server
#ssl_version=<string>
# A client certificate file for use with your server
#ssl_client_cert_file=<path_to_file>
# A file containing CA one or more certificates
#ssl_ca_file=<path_to_file>
========================================================================
4. Open Jboss studio
5. Go to File/New/OpenShiftApplication and create new app
Credentials worked. Tried it against
stg.openshift.com and
openshift.com
Cannot create a connection to OpenShift after fresh install of
rhc-tooling
--------------------------------------------------------------------------
Key: JBIDE-13522
URL:
https://issues.jboss.org/browse/JBIDE-13522
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.0.0.Final
Environment: linux fedora
Reporter: Andre Dietisheim
Assignee: Andre Dietisheim
Fix For: 4.1.0.Alpha2
The latest rhc tooling is creating an express.conf file with a double quoted
*libra_server* entry:
{code}
libra_server="openshift.redhat.com"
{code}
If you're a new user, install rhc tooling, get the above express.conf and then run
JBT, JBT will tell you that your credentials are not valid.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira