[JBoss JIRA] (JBIDE-18428) Connection wizard: get "Unknown error" instead of "Authentication error" when using bad credentials (WATCHER)
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18428?page=com.atlassian.jira.plugi... ]
Marián Labuda closed JBIDE-18428.
---------------------------------
> Connection wizard: get "Unknown error" instead of "Authentication error" when using bad credentials (WATCHER)
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18428
> URL: https://issues.jboss.org/browse/JBIDE-18428
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift, upstream
> Affects Versions: 4.2.0.CR1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Labels: connection_wizard, openshift_v2, upstream
> Fix For: 4.4.0.Final
>
> Attachments: unknown-error.png
>
>
> The issues is that OpenShift Online responds with *500 Internal Server Error* when invalid credentials are being used (where *401 Unauthorized* is expect)
> {code}
> curl -v --user adietish@redhat.com:bogus https://openshift.redhat.com/broker/rest/user* Adding handle: conn: 0xaa8a80
> * Adding handle: send: 0
> * Adding handle: recv: 0
> * Curl_addHandleToPipeline: length: 1
> * - Conn 0 (0xaa8a80) send_pipe: 1, recv_pipe: 0
> * About to connect() to openshift.redhat.com port 443 (#0)
> * Trying 50.19.249.93...
> * Connected to openshift.redhat.com (50.19.249.93) port 443 (#0)
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> * CAfile: /etc/pki/tls/certs/ca-bundle.crt
> CApath: none
> * SSL connection using TLS_RSA_WITH_AES_128_CBC_SHA
> * Server certificate:
> * subject: CN=openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US
> * start date: Jul 23 00:00:00 2014 GMT
> * expire date: Jul 27 12:00:00 2017 GMT
> * common name: openshift.redhat.com
> * issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
> * Server auth using Basic with user 'adietish(a)redhat.com'
> > GET /broker/rest/user HTTP/1.1
> > Authorization: Basic YWRpZXRpc2hAcmVkaGF0LmNvbTpib2d1cw==
> > User-Agent: curl/7.32.0
> > Host: openshift.redhat.com
> > Accept: */*
> >
> < HTTP/1.1 500
> < Cache-Control: no-cache, private
> < Content-Type: application/json; charset=utf-8
> < Date: Wed, 24 Sep 2014 10:18:21 GMT
> < ProxyTime: D=374659
> * Server Apache/2.2.15 (Red Hat) is not blacklisted
> < Server: Apache/2.2.15 (Red Hat)
> < Status: 500
> < Strict-Transport-Security: max-age=15768000, includeSubDomains
> < Vary: Accept-Encoding,User-Agent
> < X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.21
> < X-Rack-Cache: miss
> < X-Request-Id: b25500e832d6bbebb1bc7eee5e3175b4
> < X-Runtime: 0.367919
> < X-UA-Compatible: IE=Edge,chrome=1
> < Content-Length: 376
> < Connection: keep-alive
> <
> * Connection #0 to host openshift.redhat.com left intact
> {"api_version":1.7,"data":null,"messages":[{"exit_code":1,"field":null,"index":null,"severity":"error","text":"Unable to authenticate the user. Please try again and contact support if the issue persists. \nReference ID: b25500e832d6bbebb1bc7eee5e3175b4"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4,1.5,1.6,1.7],"type":null,"version":"1.7"}
> {code}
> stg.openshift.redaht.com is responding with the correct 401:
> {code}
> [adietish@localhost openshift-java-client]$ curl -v --proxy https://file.rdu.redhat.com:3128 --user adietish@redhat.com:bogus https://stg.openshift.redhat.com/broker/rest/user
> * Adding handle: conn: 0x178dae0
> * Adding handle: send: 0
> * Adding handle: recv: 0
> * Curl_addHandleToPipeline: length: 1
> * - Conn 0 (0x178dae0) send_pipe: 1, recv_pipe: 0
> * About to connect() to proxy file.rdu.redhat.com port 3128 (#0)
> * Trying 10.11.5.7...
> * Connected to file.rdu.redhat.com (10.11.5.7) port 3128 (#0)
> * Establish HTTP proxy tunnel to stg.openshift.redhat.com:443
> * Server auth using Basic with user 'adietish(a)redhat.com'
> > CONNECT stg.openshift.redhat.com:443 HTTP/1.1
> > Host: stg.openshift.redhat.com:443
> > User-Agent: curl/7.32.0
> > Proxy-Connection: Keep-Alive
> >
> < HTTP/1.0 200 Connection established
> <
> * Proxy replied OK to CONNECT request
> * Initializing NSS with certpath: sql:/etc/pki/nssdb
> * CAfile: /etc/pki/tls/certs/ca-bundle.crt
> CApath: none
> * SSL connection using TLS_DHE_RSA_WITH_AES_256_CBC_SHA
> * Server certificate:
> * subject: CN=stg.openshift.redhat.com,O=Red Hat Inc.,L=Raleigh,ST=North Carolina,C=US
> * start date: Apr 30 00:00:00 2014 GMT
> * expire date: May 04 12:00:00 2016 GMT
> * common name: stg.openshift.redhat.com
> * issuer: CN=DigiCert SHA2 High Assurance Server CA,OU=www.digicert.com,O=DigiCert Inc,C=US
> * Server auth using Basic with user 'adietish(a)redhat.com'
> > GET /broker/rest/user HTTP/1.1
> > Authorization: Basic YWRpZXRpc2hAcmVkaGF0LmNvbTpib2d1cw==
> > User-Agent: curl/7.32.0
> > Host: stg.openshift.redhat.com
> > Accept: */*
> >
> < HTTP/1.1 401
> < Date: Wed, 24 Sep 2014 10:19:22 GMT
> * Server Apache/2.2.15 (Red Hat) is not blacklisted
> < Server: Apache/2.2.15 (Red Hat)
> < X-Powered-By: Phusion Passenger (mod_rails/mod_rack) 3.0.21
> * Authentication problem. Ignoring this.
> < WWW-Authenticate: Basic realm="Application"
> < X-UA-Compatible: IE=Edge,chrome=1
> < Cache-Control: no-cache, private
> < X-Request-Id: 5217138e18f0e036b1880d006e4c3cb6
> < X-Runtime: 0.569233
> < X-Rack-Cache: miss
> < Status: 401
> < Content-Length: 27
> < Content-Type: text/html; charset=utf-8
> < Vary: Accept-Encoding,User-Agent
> < Strict-Transport-Security: max-age=15768000, includeSubDomains
> < ProxyTime: D=574882
> <
> HTTP Basic: Access denied.
> * Connection #0 to host file.rdu.redhat.com left intact
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22604) CDK server adapter stuck at starting
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22604?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22604.
---------------------------------
[~jrichter1] and I agreed that this JIRA is sufficiently verified and can be closed. Closing.
> CDK server adapter stuck at starting
> ------------------------------------
>
> Key: JBIDE-22604
> URL: https://issues.jboss.org/browse/JBIDE-22604
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.4.0.Final
> Environment: development-suite-1.0.0-GA-20160615-188-bundle-installer.exe
> devstudio 10.0.0.GA-a
> CDK 2.1.RC3
> Reporter: Jan Richter
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.0.Final
>
>
> I have installed the development suite using the all-in-1 installer (on 3 different windows machines now). Every time I try to start CDK using the server adapter it gets stuck on 'starting'.
> In fact the CDK does start up, openshift is running, but no connection is created + the server adapter is marked as starting and the job (starting CDK) is spinning until it hits the timeout.
> Strange thing is - stopping the job/server adapter at this point will first create the desired openshift connection and then CDK wil stop.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBDS-3903) Platform Installer does not Setup Docker Env-Vars
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3903?page=com.atlassian.jira.plugin.... ]
Xavier Coulon updated JBDS-3903:
--------------------------------
Fix Version/s: 10.0.1.GA
> Platform Installer does not Setup Docker Env-Vars
> -------------------------------------------------
>
> Key: JBDS-3903
> URL: https://issues.jboss.org/browse/JBDS-3903
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: docker
> Affects Versions: 10.0.0.Alpha1
> Environment: Windows
> Reporter: Thomas Mäder
> Assignee: Xavier Coulon
> Fix For: 10.0.1.GA
>
>
> I have installed CDK, etc. from the "all in one" installer. Later, I tried to use Docker tooling. I opened the view "Docker Explorer". There was no connection shown. I tried to add a new one, but the system did not detect my default connection.
> Later, I ran "Docker Quickstart Terminal" from the start menu. Now the "New Connection" dialog in docker explorer picked up the default connection.
> As a user, I have no indication that I have to run the docker terminal in order to use the docker tooling in eclipse. If there are environment variables to be set up, the installer should do so. It is the reasonable expectation on Windows.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22187) Connection wizard: Should not be able to create duplicate Openshift connections
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22187?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-22187.
------------------------------
Verified in Devstudio 10.0.0.GA (B33)
> Connection wizard: Should not be able to create duplicate Openshift connections
> -------------------------------------------------------------------------------
>
> Key: JBIDE-22187
> URL: https://issues.jboss.org/browse/JBIDE-22187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jeff MAURY
> Assignee: Viacheslav Kabanovich
> Priority: Minor
> Labels: connection_wizard, openshift_v3
> Fix For: 4.4.0.Final
>
>
> It is possible to create 2 identical Openshift connections (same url and credentials). They will appear as 2 tree items in the Openshift explorer but when you use various wizards, only a single items is show. I think we should not allow the creation of such identical connections as the name is composed of those elements.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22604) CDK server adapter stuck at starting
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22604?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-22604:
----------------------------------
Workaround Description:
The way this was fixed for CDK 2.1 and devstudio 10 means that by default, sshfs (shared folder) will not be used. There is a custom Vagrantfile with sshfs configured, but if you use it with devstudio, you will still experience this issue - cdk will not start properly in devstudio.
If you still want to use sshfs in devstudio, there is a workaround:
1. Start CDK with sshfs setup from CLI:
{code}
cd components/rhel/misc/shared_folder/rhel-ose
vagrant up
{code}
2. Set up CDK in devstudio (make sure to use this Vagrantfile: components/rhel/misc/shared_folder/rhel-ose/Vagrantfile) and start it
Devstudio will notice it's already running and so it will mark it as Started immediately, thus circumventing the whole startup which would fail in this case. You can then use the cdk environment as normally - openshift connection and docker connection will both work normally.
was:
The way this was fixed for CDK 2.1 and devstudio 10 means that by default, sshfs (shared folder) will not be used. There is a custom Vagrantfile with sshfs configured, but if you use it with devstudio, you will still experience this issue - cdk will not start properly in devstudio.
If you still want to use sshfs in devstudio, there is a workaround:
1. Start CDK with sshfs setup from CLI:
{code}
cd components/rhel/misc/shared_folder/rhel-ose
vagrant up
{code}
2. Set up CDK in devstudio and start it
Devstudio will notice it's already running and so it will mark it as Started immediately, thus circumventing the whole startup which would fail in this case. You can then use the cdk environment as normally - openshift connection and docker connection will both work normally.
> CDK server adapter stuck at starting
> ------------------------------------
>
> Key: JBIDE-22604
> URL: https://issues.jboss.org/browse/JBIDE-22604
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.4.0.Final
> Environment: development-suite-1.0.0-GA-20160615-188-bundle-installer.exe
> devstudio 10.0.0.GA-a
> CDK 2.1.RC3
> Reporter: Jan Richter
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.0.Final
>
>
> I have installed the development suite using the all-in-1 installer (on 3 different windows machines now). Every time I try to start CDK using the server adapter it gets stuck on 'starting'.
> In fact the CDK does start up, openshift is running, but no connection is created + the server adapter is marked as starting and the job (starting CDK) is spinning until it hits the timeout.
> Strange thing is - stopping the job/server adapter at this point will first create the desired openshift connection and then CDK wil stop.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22604) CDK server adapter stuck at starting
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22604?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-22604:
----------------------------------
Workaround Description:
The way this was fixed for CDK 2.1 and devstudio 10 means that by default, sshfs (shared folder) will not be used. There is a custom Vagrantfile with sshfs configured, but if you use it with devstudio, you will still experience this issue - cdk will not start properly in devstudio.
If you still want to use sshfs in devstudio, there is a workaround:
1. Start CDK with sshfs setup from CLI:
{code}
cd components/rhel/misc/shared_folder/rhel-ose
vagrant up
{code}
2. Set up CDK in devstudio and start it
Devstudio will notice it's already running and so it will mark it as Started immediately, thus circumventing the whole startup which would fail in this case. You can then use the cdk environment as normally - openshift connection and docker connection will both work normally.
> CDK server adapter stuck at starting
> ------------------------------------
>
> Key: JBIDE-22604
> URL: https://issues.jboss.org/browse/JBIDE-22604
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, upstream
> Affects Versions: 4.4.0.Final
> Environment: development-suite-1.0.0-GA-20160615-188-bundle-installer.exe
> devstudio 10.0.0.GA-a
> CDK 2.1.RC3
> Reporter: Jan Richter
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.4.0.Final
>
>
> I have installed the development suite using the all-in-1 installer (on 3 different windows machines now). Every time I try to start CDK using the server adapter it gets stuck on 'starting'.
> In fact the CDK does start up, openshift is running, but no connection is created + the server adapter is marked as starting and the job (starting CDK) is spinning until it hits the timeout.
> Strange thing is - stopping the job/server adapter at this point will first create the desired openshift connection and then CDK wil stop.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months