[USERGRID-228] Portal should not give username/password error when error was due to some other problem

• Type: Story
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 2.1.0
• Component/s: Portal
• Epic Link: Portal -fit and finish
• Sprint: Usergrid 23
• Assignee: ryan bridges
• Reporter: Rod Simpson
• Created: 16/Sep/14 15:01
• Updated: 02/Feb/16 21:49
• Resolved: 23/Jun/15 14:19

Description

Sometimes when Usergrid starts it errors gracefully if one of the ports is in use (7000) sometimes it gives a timeout (8080) and sometimes it works (8080) even though the port is used but then when you try the portal it tells you the username/password was not valid when in fact the error is a 501 on ‘OPTIONS’, though it could be a different error depending on what is already using the port (screenshot below). This same behavior happens if the port cannot be reached. So, the questions are:
1) Can we configure all the different ports using the Launcher JAR? Including Cassandra?
2) Can we update the portal to display something other than invalid user/name when this happens?