[ https://issues.jboss.org/browse/JBIDE-17615?page=com.atlassian.jira.plugi... ] Martin Malina edited comment on JBIDE-17615 at 8/2/16 7:28 AM: --------------------------------------------------------------- I was waiting for jboss.org change password page to be fixed to verify this: ORG-3476 But today I realized that I can use a Red Hat Developer account instead. So I used a new social account that I created at developers.redhat.com using my github account. I was able to download EAP normally - that verified JBIDE-21801 is fixed. But then I tried the scenario when I first go through the dialog and after entering the credentials in Eclipse and just before the actual download starts, I changed my rh developer password. I got a pop up asking me for credentials. !reenter-password.png! But now I was unable to make it work even if I provided the new password. (And when I finally cancelled this and went through the dialog again, I was able to download using the new password.) Note that it's not clear from this dialog what domain I'm using, but I assume it should use the same domain that I used originally. I would argue that the account name should probably be locked down as well at this point. was (Author: mmalina): I was waiting for jboss.org change password page to be fixed to verify this: ORG-3476 But today I realized that I can use a Red Hat Developer account instead. So I used a new social account that I created at developers.redhat.com using my github account. I was able to download EAP normally - that verified JBIDE-21801 is fixed. But then I tried the scenario when I first go through the dialog and after entering the credentials in Eclipse and just before the actual download starts, I changed my rh developer password. I got a pop up asking me for credentials. But now I was unable to make it work even if I provided the new password. (And when I finally cancelled this and went through the dialog again, I was able to download using the new password.) Note that it's not clear from this dialog what domain I'm using, but I assume it should use the same domain that I used originally. I would argue that the account name should probably be locked down as well at this point. -- This message was sent by Atlassian JIRA (v6.4.11#64026)