Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[bug] Multiple login support does not work #42

Open
GregSutcliffe opened this issue May 8, 2013 · 2 comments
Open

[bug] Multiple login support does not work #42

GregSutcliffe opened this issue May 8, 2013 · 2 comments
Assignees
Milestone

Comments

@GregSutcliffe
Copy link

As openDias is a webapp, I should be able to log in from multiple places. But here's what actually happens:

[to reproduce]
Navigate to opendias on computer 1
Log in with correct user/password (which succeeds)
Navigate to opendias on computer 2
Log in with correct user/password (fails silently)

[what should happen]
I should be allowed to log in. I'm not too bothered if the older session is invalidated, as I've obviously changed locations or something. Note this is definitely not a case of wrong-password, as that correctly pops up a box saying "wrong user/pass". This happily accepts my input, but doesn;t actually log me in.

[current workaround]
I managed to reset my session by logging in to the opendias box and restarting the service. This raises a secondary question about whether user sessions should survive a process reboot ;)

@ghost ghost assigned WayneBooth May 8, 2013
@WayneBooth
Copy link
Member

I've tested this out but am unable to replicate it.
What happens on the second login machine? You said fails silently, but how does the problem manifest itself?
Any chance of some logs (in verbose mode) of the first followed by the second login attempt?

The session management was specifically designed not to survive a reboot (it's all kept in memory). Since I'd not expect openDias to be restarted often I would have though this was OK. Do you think this is something that needs addressing?

@GregSutcliffe
Copy link
Author

The result on the second machine is that you are kicked back to the not-logged-in version of the homepage. You don't get a message like "incorrect password" so I think it tries to login and then drops back out. I'll try to gather some logs over the weekend.

Session management is fine in-memory, so long as that's deliberate. I was merely posting my workaround in case others hit the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants