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.

Sign up for GitHub

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

Jump to bottom

allow to be connected to more than one conference #41

Open
maddingue opened this issue Dec 7, 2012 · 1 comment
Open

allow to be connected to more than one conference #41

maddingue opened this issue Dec 7, 2012 · 1 comment

Comments

@maddingue
Copy link
Collaborator

Because the session ID currently is stored in the "users" table, one can not be logged on more than one conference on an Act instance. Although not a big issue, it is very annoying when one attends to several conferences and has to sign out and sign in each time.
HaraldJoerg referenced this issue in act-psgi/Act May 2, 2019
@HaraldJoerg
Bugfix: After providing registration data, an user is now logged in.
7fee94e 
Before that, the session cookie granted by the registration page was
1) only valid for the registration page and 2) already expired.
As a drive-by this also should close book:#41.
@HaraldJoerg
Copy link
Contributor

It is correct, the session ID is stored in the "users" table. But actually, you don't have to sign out and sign in to attend to different conferences, because this table is globally used for all conferences.

What you can't do is to be logged in from different devices, e.g. from your laptop and your mobile phone, at the same time, which you might want to do while you are at a conference to check/change your personal schedule.

waterkip pushed a commit to waterkip/Act that referenced this issue Nov 1, 2019
@HaraldJoerg @waterkip
Bugfix: After providing registration data, an user is now logged in.
5e01fe5 
Before that, the session cookie granted by the registration page was
1) only valid for the registration page and 2) already expired.
As a drive-by this also should close book:book#41.
waterkip pushed a commit to waterkip/Act that referenced this issue Nov 2, 2019
@HaraldJoerg @waterkip
Bugfix: After providing registration data, an user is now logged in.
2d4ba7d 
Before that, the session cookie granted by the registration page was
1) only valid for the registration page and 2) already expired.
As a drive-by this also should close book:book#41.
waterkip pushed a commit to waterkip/Act that referenced this issue Nov 2, 2019
@HaraldJoerg @waterkip
Bugfix: After providing registration data, an user is now logged in.
0c537cd 
Before that, the session cookie granted by the registration page was
1) only valid for the registration page and 2) already expired.
As a drive-by this also should close book:book#41.
waterkip pushed a commit to waterkip/Act that referenced this issue Nov 2, 2019
@HaraldJoerg @waterkip
Bugfix: After providing registration data, an user is now logged in.
cab2b55 
Before that, the session cookie granted by the registration page was
1) only valid for the registration page and 2) already expired.
As a drive-by this also should close book:book#41.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@maddingue @HaraldJoerg