Closed nichtich closed 3 years ago
To be honest, I sometimes get confused myself with the different subpages of login-server. These are my thoughts at the moment:
/
and the user is not logged in, it should redirect to /login
./account
should actually be under /
(or /
redirects to /account
if the user is logged in)./
should be somewhere, maybe shown on /login
?When accessing
/
and the user is not logged in, it should redirect to/login
What's now under/account
should actually be under/
(or/
redirects to/account
if the user is logged in).
The text shown at /
could be put under "/about" or "/help" (see #27) and /
perform a redirect to /login
or account
. To better organize the subpages I recommend a header navigation with three pages:
/
): general information about the service/about
is already an API endpoint for information about the server, so we should use /help
instead. But in the navigation it can still be called "About", that definitely works better.I added the header and restructured everything a bit (haven't looked at sessions yet though). Please take a look, @nichtich:
https://user-images.githubusercontent.com/3275148/104302021-98484e80-54c8-11eb-96fc-f1bd23a76331.mov
- sessions or "clients": active sessions. This would be more informative if we had information about the client a session originated in. We could add a static list of known client applications (BARTOC, coli-conc, coli-rich), at least.
I'm not sure how to determine where a session originated. I guess 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.