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

Save and show where a session originated from #70

Closed
nichtich opened this issue Jan 12, 2021 · 1 comment
Closed

Save and show where a session originated from #70

nichtich opened this issue Jan 12, 2021 · 1 comment
Labels
feature undefined
Milestone

Comments

@nichtich
Copy link
Member

Split from #66

Active sessions should indicate the client using the session. As we don't require clients to have been registered, this information can only be guessed:

we could save the referrer (i.e. when the user logs in from Cocoda). My suggestion: On the server, when either /login or /login/:provider are requested and a referrer other than the login server URL is given, and if the user is not currently logged in, save that referrer inside a field in the session.

This should be enough to get a client URL. Users can click on the URL to find out more details.

@nichtich nichtich added the feature undefined label Jan 12, 2021
@nichtich nichtich added this to the 0.5.0 milestone Jan 12, 2021
@nichtich
Copy link
Member Author

nichtich commented Jan 13, 2021

Session and WebSocket ID do not need to be shown but client application names would be helpful (#72).

@stefandesu stefandesu modified the milestones: 0.5.0, 0.4.0 Jan 14, 2021
stefandesu added a commit that referenced this issue Jan 14, 2021
Will show the application name after implemented in #72.
stefandesu added a commit that referenced this issue Jan 18, 2021
Reword help about data sharing
#27, #66, #70, #72
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature undefined
Projects
None yet
Development

No branches or pull requests

2 participants