[ https://issues.jboss.org/browse/JBIDE-8250?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-8250: ----------------------------------------- Furthermore the error text is bad english. It says "Could not connection to..." -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8250?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-8250: ----------------------------------------- the basic reason for this behavior is 2-fold: 1) Bad response from Deltacloud server I request an unknown instance and provide the credentials you entered in the dialog. If I get 404 back, I know credentials are valid. If I get 403 back, I know that the credentials were invalid. If I get another error, I display it since this might be some other error: server timeouted, server crashed, etc. The latest deltacloud server responds with 500 (internal server error) if I request an unknown resource while using invalid credentials. I expect 403. I reported this to the deltacloud jira https://issues.apache.org/jira/browse/DTACLOUD-14. 2) Any error-response should show "connection test failed" in the title area I did only treat 403 response as connection failure. All other cases (other errors, too) were treated as connection successful. I provided a 1-liner patch since I belive that the error-dialog should still appear on any error-response that is not 403. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8250?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-8250: ------------------------------------ Attachment: CredentialsTest.patch corrected patch, testing for 401 (not 403) as discussed in https://issues.apache.org/jira/browse/DTACLOUD-14 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8250?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-8250: ------------------------------------ Steps to Reproduce: 1) create a new cloud 2) use a valid url 3) use invalid credentials 4) hit "Test" Result: You get an error dialog that tells you that there was an authorization error. The title are of the wizard says the test was successful. (see screenshot) Expected: No error dialog, title says that the test failed. was: 1) create a new cloud 2) use a valid url 3) use invalid credentials 4) hit "Test" Result: You get an error dialog that tells you that there was an authorization error. The title are of the wizard says the test was successful. (see screenshot) Expected: No error dialog, title are says that the test failed. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8250?page=com.atlassian.jira.plugin... ] Max Rydahl Andersen commented on JBIDE-8250: -------------------------------------------- Looks innocent enough ;) go for branch/trunk. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8250?page=com.atlassian.jira.plugin... ] Andre Dietisheim resolved JBIDE-8250. ------------------------------------- Fix Version/s: 3.2.1 Resolution: Done committed to TRUNK(3.2.1) and BRANCH (CR2) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/JBIDE-8250?page=com.atlassian.jira.plugin... ] Libor Zoubek closed JBIDE-8250. ------------------------------- -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira