Description of problem:
After leaving the system overnight, logged into the Satellite UI (on the first step, 1A), when we came back and tried to start configuring the deployment, it didn't recognize that we had been timed out. We were able to enter a name and description for our new deployment and click Next, and then when trying to pick an org, it didn't offer anything (no orgs found), and wouldn't let us make any (the create new button was disabled). Refreshing the page brought us back to the login screen, and after starting over, we were able to find an org, or make one if needed.

Version-Release number of selected component (if applicable):
RHCI-6.0-RHEL-7-20150630.t.0-RHCI-x86_64-dvd1.iso

How reproducible:
I would guess 100%

Steps to Reproduce:
1. log into Sat UI after installing
2. Create new deployment
3. Wait for session to time out (however long that is)
4. Resume deployment configuration

Actual results:
While I was expecting to have been timed out, when I came back to the Satellite UI the next day, I still appeared to be logged in, and I was able to interact with the UI. After entering in a name and description for 1A, I clicked Next, and got to 1B. The org table couldn't find any orgs though, and the Create New button was disabled.

Expected results:
To either be able to come back to a session and pick up where I left off, or have it time out and tell me so, rather than me having to figure it out when things silently stop working.

Additional info: