[jbosstools-issues] [JBoss JIRA] (JBIDE-11431) Cannot log into user account, invalid json being reported

[ https://issues.jboss.org/browse/JBIDE-11431?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-11431 at 3/28/12 1:51 PM: ------------------------------------------------------------------- back in issue JBIDE-11354 that we could not reproduce, there was a very similar reponse that could not be unmarshalled: {code} "data":{ "user_info":{ "rhlogin":"spousty+mongo@redhat.com", "uuid":"8e863f72f2f743b58003257077d700dd", "rhc_domain":"rhcloud.com", "vip":false, "ssh_type":"", "max_gears":5, "ssh_keys":{}, "ssh_key":"", "consumed_gears":0, "namespace":"spousty0mongo" }, "app_info":{ } } {code} *ssh_type* and *ssh_key* are both *""*: {code} "ssh_type":"", "ssh_key":"" {code} I suspect inconsistency in the service since we're not seeing these messages. Pretty much these same applies IMHO to JBIDE-11418 where the usual workflow is that the PaaS usually responds with a *404* and sometimes obviously with a *200*. was (Author: adietish): back in issue JBIDE-11354 that we could not reproduce, there was a very similar reponse that could not be unmarshalled: {code} "data":{ "user_info":{ "rhlogin":"spousty+mongo@redhat.com", "uuid":"8e863f72f2f743b58003257077d700dd", "rhc_domain":"rhcloud.com", "vip":false, "ssh_type":"", "max_gears":5, "ssh_keys":{}, "ssh_key":"", "consumed_gears":0, "namespace":"spousty0mongo" }, "app_info":{ } } {code} *ssh_type* and *ssh_key* are both *""*: {code} "ssh_type":"", "ssh_key":"" {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira