Uploaded image for project: 'Tools (JBoss Tools)'
  1. Tools (JBoss Tools)
  2. JBIDE-13558

CLONE - Cannot create a connection to OpenShift after fresh install of rhc-tooling

    XMLWordPrintable

Details

    • Hide

      1. ASSERT: make sure you dont have an existing express.conf (/etc/openshift/express.conf or ~/.openshift/express.conf)
      2. EXEC: do a fresh install of the rhc tools
      3. ASSERT: you get a new /etc/openshift/express.conf with the libra_server value double quoted:

      libra_server="openshift.redhat.com"
      

      4. EXEC: Launch "New OpenShift Applcation" from New wizards (or Central) and create a new connection: Provide username and host, hit "next"

      Result:

      The wizard tells you that your credentials are not valid.

      Looking more closely at the default server that you get suggested, you'll see that host is double quoted.

      Expected result:
      The wizard is either automagically removing the double quotes before using the host or telling you accurately that it could not reach the host.

      Show
      1. ASSERT: make sure you dont have an existing express.conf (/etc/openshift/express.conf or ~/.openshift/express.conf) 2. EXEC: do a fresh install of the rhc tools 3. ASSERT: you get a new /etc/openshift/express.conf with the libra_server value double quoted: libra_server= "openshift.redhat.com" 4. EXEC: Launch "New OpenShift Applcation" from New wizards (or Central) and create a new connection: Provide username and host, hit "next" Result: The wizard tells you that your credentials are not valid. Looking more closely at the default server that you get suggested, you'll see that host is double quoted. Expected result: The wizard is either automagically removing the double quotes before using the host or telling you accurately that it could not reach the host.
    • Hide

      remove the double quotes from the host-name

      Show
      remove the double quotes from the host-name
    • Hide
      Users of the latest rhc tools (1.4.7 and older) can run into the situation where they cannot succesfully authenticate against OpenShift when using JBoss Tools. The tools keep reporting invalid credentials.
      The rhc command line tools create new configuration files (/etc/openshift/express.conf and ~/.openshift/express.conf) when they're told to do the initial setup.
      Version 1.4.7 used a new format where values were within double quotes.
      The Eclipse tooling could not handle these and tried to connect to an invalid host ("openshift.redhat.com").
      It then reported invalid credentials since it could not connect to OpenShift.
      In Alpha1 JBoss Tools can now read these new configuration files.
      Show
      Users of the latest rhc tools (1.4.7 and older) can run into the situation where they cannot succesfully authenticate against OpenShift when using JBoss Tools. The tools keep reporting invalid credentials. The rhc command line tools create new configuration files (/etc/openshift/express.conf and ~/.openshift/express.conf) when they're told to do the initial setup. Version 1.4.7 used a new format where values were within double quotes. The Eclipse tooling could not handle these and tried to connect to an invalid host ("openshift.redhat.com"). It then reported invalid credentials since it could not connect to OpenShift. In Alpha1 JBoss Tools can now read these new configuration files.

    Description

      The latest rhc tooling is creating an express.conf file with a double quoted libra_server entry:

      libra_server="openshift.redhat.com"
      

      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.

      Attachments

        Issue Links

          Activity

            People

              adietish@redhat.com André Dietisheim
              adietish@redhat.com André Dietisheim
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: